Support for pseudo child-tickets and a visual reference to these within a parent ticket
This plugin modifies the ticket description box and adds a child ticket listing table and a 'create' button for adding new child tickets.
Having child-tickets is useful when multiple releases need to be managed. For example for a single 'bug-report' ticket and a single 'bug-fix' ticket for each milestone/branch of development, for managing sub-tasks of an issue and for managing 'bug-fixes' required when developing a new (larger) enhancement.
It is possible to control in trac.ini the following aspects of child-ticket creation/viewing:
- allow/disallow child-tickets for a certain type of ticket
- define the table headers displayed in the parent ticket
- define a default for the child type to be created / restrict the type of child-tickets
- define which fields are inherited by child-tickets
Some time ago I came across the problem of how to manage child tickets in a meaningful fashion, we were using coderanger's original MasterTicketsPlugin and it was great until we started to allow tickets to be viewed and created by people outside of our immediate development group. We found that people who were not familiar with our processes would simply create child tickets of the wrong 'type' and needed some help in getting it right. In addition, users found that the lack of visual information (ie. what are this tickets child tickets?) was also a hindrance.
Under Trac 0.10 I had to modify the ticket.html templates to get this working in any 'pretty' sense so I have not provided support for 0.10. As of 0.11, the ITemplateStreamFilter allows this to be incorporated nicely into a neat plugin.
To keep the plugin compact and simple and to allow future compatibility with different CSS schemes, I have simply 'pinched' the existing CSS classes for generating the table and its components.
If you have any issues, create a new ticket.
Download the zipped source from here.
General instructions on installing Trac plugins can be found on the TracPlugins page.
The plugin makes use of the 'ticket-custom' field and so requires no extra database tables to be created. The following fields are required in the trac.ini file:
[components] childtickets.* = enabled [ticket-custom] parent = text parent.format = wiki parent.label = Parent ID [childtickets] # 'enhancements': child tickets will typically be bug-fix tickets with the same milestone, component and keywords. parent.enhancement.allow_child_tickets = true parent.enhancement.restrict_child_type = bug-fix, task parent.enhancement.table_headers = type, status, owner, summary parent.enhancement.inherit = milestone, component, keywords # 'bug-report': child tickets will typically be bug-fix parent.bug-report.allow_child_tickets = true parent.bug-report.default_child_type = bug-fix parent.bug-report.table_headers = type, priority, owner, summary, milestone parent.bug-report.inherit = component, keywords # 'issue': child tickets will typically be task tickets with no default milestone. parent.issue.allow_child_tickets = true parent.issue.restrict_child_type = task parent.issue.table_headers = type, status, owner, summary, milestone # 'bug-fix': child tickets are not allowed. parent.bug-fix.allow_child_tickets = false # 'task': child tickets are not allowed. parent.task.allow_child_tickets = false
See table below for a generic description of the options.
|parent.parent-type.allow_child_tickets||Define whether child tickets are allowed or not||False|
|parent.parent-type.table_headers||List of column headers for display in parent ticket||summary, owner|
|parent.parent-type.default_child_type||Default child type||See [ticket] section of trac.ini (default_type)|
|parent.parent-type.restrict_child_type||A list of possible child types, trying to create a child of a different 'type' will create an error. As of version 1.1.0, if this option is used, a list of submit buttons will be rendered allowing the user to decide which type of child ticket he/she wants to create.||None|
|parent.parent-type.inherit||Define a list of inherited fields.||Default: None|
|default.max_depth||Limit the creation of too deep a hierarchy.||5|
Known Issues / Caveats
- If you change the behaviour of the parent type (using for example allow_child_tickets/restrict_child_type) and tickets already have child tickets assigned to them, you will not receive a warning about any possible conflicts until you try and modify any of the child tickets.
- If a parent ticket is restricted in some way that no further child tickets can be generated for that ticket 'type', you'll continue to see a list of child tickets but the 'Create' button will be missing.
- The 'parent.<type>.inherit' option ensures fields are inherited by child tickets. However, all child tickets regardless of type as defined by 'restrict_child_type' will inherit these values.
Some examples here.
- 15128 by rjollos on 2015-12-19 23:57:49
2.5.4dev: Refactor database queries
- 15100 by rjollos on 2015-12-07 03:58:46
2.5.4dev: Cleanup whitespace
- 15066 by rjollos on 2015-11-19 04:48:51
2.5.4dev: Revise installation requirements
Enforce Trac >= 1.0. Genshi and Python version is enforced
- bug-report-example.jpg (45.7 KB) - added by walnut 6 years ago.
- issue-example.jpg (34.3 KB) - added by walnut 6 years ago.
- MultipleChildType.png (7.1 KB) - added by walnut 5 years ago.
(27.4 KB) -
added by walnut 5 years ago.
The ProgressMeterMacro also provides some nice features
- NewChildTicketTable.png (40.1 KB) - added by walnut 5 years ago.
Download all attachments as: .zip