Changes between Version 1 and Version 2 of ChildTicketsPlugin/Examples
- Timestamp:
- Jan 5, 2012, 8:44:35 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ChildTicketsPlugin/Examples
v1 v2 7 7 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 ... 8 8 9 [[Image( bug-report-example.jpg)]]9 [[Image(wiki:ChildTicketsPlugin:bug-report-example.jpg)]] 10 10 11 11 === Handling sub-tasks from a single issue === … … 13 13 Probably self explanatory: you have something that needs to be done by several different people. Split it up into sub-tasks. 14 14 15 [[Image( issue-example.jpg)]]15 [[Image(wiki:ChildTicketsPlugin:issue-example.jpg)]] 16 16 17 17 === A New Feature generates bugs === … … 23 23 If you are using the above option, the available child types will be rendered as individual buttons. 24 24 25 [[Image( MultipleChildType.png)]]25 [[Image(wiki:ChildTicketsPlugin:MultipleChildType.png)]] 26 26 27 27 === Creating a Progress Bar for Child Tickets === … … 35 35 Then the following will appear in the ticket description: 36 36 37 [[Image( progmeter_ticket.png)]]37 [[Image(wiki:ChildTicketsPlugin:progmeter_ticket.png)]]