Fossil SCM
Tickets should have an 'assigned_to' field
f6b83821d6a6fa1…
· opened 16 years, 1 month ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Important
- Resolution
- Works_As_Designed
- Subsystem
- —
- Created
- Feb. 17, 2010 4:43 a.m.
In a multi-developer environment, it is useful to assign tickets to people. Fossil doesn't currently have a way to assign them.
jeremy_c added on 2010-02-17 12:36:30:
The fossil ticket system is very versitle and does have the ability to assign tickets to people in a multi-developer environment, it's just not default.
Simply add a new field named assign_to, create a new list of assignable people and update your edit/view templates.
You can do about anything with the fossil ticket system.
anonymous claiming to be Michael McDaniel added on 2010-02-18 16:56:34:
I read Jeremy's "how to" and understand the words, though still do not understand how to implement the feature I would also find useful.
Please explain again how to implement, using language which assumes zero a priori knowledge. New field/list where ? edit/view templates ? where/what are those ? etc. Maybe this is a candidate for the wiki or embedded doc pages. thanks
ron added on 2010-02-18 17:37:17:
Instructions on what to do are here.
anonymous claiming to be Michael McDaniel added on 2010-02-18 18:34:18:
Thank you for the details, Ron - worked fine.
anonymous added on 2011-04-08 17:46:00 UTC: What if one wanted a dynamic list of certain users in the table (instead of a static one as specified in the example). It seems th1 doesn't have a way to do a sql command.
Comments (1)
Closing as part of periodic cleanup.