|Version 2 (modified by walnut, 4 years ago) (diff)|
Handling multiple bug-fixes for single bug-report
In my last job using trac with svn, we had a branch of development for each milestone of development plus a 'special' milestone to assign for hotfix/patches. Rather than creating a single 'bug-fix' ticket and commenting on the ticket that the fix had been applied to milestone X on branch X, milestone Y on branch Y, etc..., we would create a single 'bug-report' ticket (with version info but no milestone) and this ticket would, after assessment from developers/project-mgr, have a bug-fix child-ticket created per milestone - each with its own life-cycle, priority, (sometimes) developer, etc ...
Handling sub-tasks from a single issue
Probably self explanatory: you have something that needs to be done by several different people. Split it up into sub-tasks.
A New Feature generates bugs
When developing a new feature (a single ticket), our developers would 'finish' the feature and pass it to our testing department. The feature, on the whole, might be OK but require several days testing. Within that time several bugs are generated as a direct result of this new feature. It makes no sense to pass the original feature ticket back to the developers (the feature has not been 'rejected' and is still in testing!), so instead, the testing tem can make 'bug-fix' child-tickets for this parent ticket. The feature might even be released with known bugs but at least they're recorded and owned by someone/somewhere!
Using the 'parent.type.restrict_child_type' Option
If you are using the above option, the available child types will be rendered as individual buttons.
Creating a Progress Bar for Child Tickets
If you have a lot of child tickets for one parent, and want an overview of those tickets, you can use the ProgressMeterMacro as provided by qwp0. In order to use this, simply provide the 'parent' as the only search query. For example, if you put the following macro definition in your ticket description:
Then the following will appear in the ticket description: