Opened 13 years ago
Last modified 8 years ago
#9550 new enhancement
Ticket should be divisible
|Reported by:||Owned by:|
|Severity:||normal||Keywords:||field links relations|
|Cc:||itamarost@…, joao.antunes@…, leho@…||Branch:|
Sometimes tickets are entered into the ticket system that contain more than one issue. These tickets should be diversible. When something like this happens I create new tickets with the parts and assign them to their owners. The all new ticket ids are put into the 'parent'. It would be nice if trac could help with this task and manage a parent/child relationship between tickets. When childs of a ticket are created the parent ticket should be set on hold until all children are resolved. The parent could show a progress bar or something. Notifications for children should be send to their subscribers and the subscribers of the parent ticket.
Change History (6)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
|Keywords:||field links relations added|
Actually a duplicate of #886.
However, as the present ticket nicely summarizes the design discussion that happened there, and given the fact that #886 has grown quite long, let's keep the present ticket for discussing the implementation details, on top of ticket-links.
So this ticket depends on #31, and I already can see a few children tickets ;-)
- make the "progress bar" more easily reusable in other contexts than the milestone
- in a first step we can have the "parent/children" ticket simply listed below Ticket relations (a la Redmine, cf. ticket:31#comment:147), but in a second step, have a specialized rendering with a milestone-like progress bar; this is probably related to some ideas from FieldRefactoring.
- description/comment button for creating sub-tickets from the content; from the wiki content, we'd take the top-level list and divide it in as many sub-tickets as items; the tickets are not created right away, rather we're just in a preview mode (extend the new ticket form so that we can create multiple tickets in one go)
comment:3 by , 13 years ago
comment:4 by , 12 years ago
comment:5 by , 10 years ago
comment:6 by , 8 years ago
Related to #31. Duplicate?