Edgewall Software
Modify ↓

Opened 16 years ago

Last modified 8 months ago

#9550 new enhancement

Ticket should be divisible

Reported by: stephan@… Owned by:
Priority: normal Milestone: next-major-releases
Component: ticket system Version:
Severity: normal Keywords: field links relations
Cc: itamarost@…, joao.antunes@…, leho@…, chealer@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Philippe Cloutier <chealer@…>)

Sometimes a ticket which reports more than one issue is created. When something like this happens I create new tickets with the parts and assign them to their owners. Then the identifiers of these new ticket are put into the 'parent'.

Such tickets should be divisible. It would be nice if Trac could help with this task and manage a parent/child relationship between tickets. When children 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 sent to their subscribers and the subscribers of the parent ticket.

Attachments (0)

Change History (7)

comment:1 by Remy Blank, 16 years ago

Related to #31. Duplicate?

comment:2 by Christian Boos, 16 years ago

Keywords: field links relations added
Milestone: → next-major-0.1X
Owner: set to Christian Boos

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 Itamar Oren, 16 years ago

Cc: itamarost@… added

comment:4 by joao.antunes@…, 16 years ago

Cc: joao.antunes@… added

comment:5 by lkraav <leho@…>, 14 years ago

Cc: leho@… added

comment:6 by Ryan J Ollos, 11 years ago

Owner: Christian Boos removed

comment:7 by Philippe Cloutier <chealer@…>, 8 months ago

Cc: chealer@… added
Description: modified (diff)

Stephan: The situation you report sounds familiar, yet I am not sure I agree with your suggestions. It would help analyzing to provide concrete examples of such issues.

It’s also unclear how a progress bar would behave in such a situation.

This comment is from Philippe "Chealer" Cloutier. I am subscribing to this ticket, but notifications seem to be broken, and I struggle to display my full email address or link to my contact information from this comment. My email address is available on Kune ni povos’s contact page. All of my comments and contributions in this ticket are offered under the terms of CC0 1.0 (unless otherwise noted).

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.