Changes between Version 1 and Version 2 of ChildTicketsPlugin
- Timestamp:
- Apr 19, 2010, 3:15:05 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ChildTicketsPlugin
v1 v2 97 97 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 ... 98 98 99 [[Image( bug-report-example.jpg?format=raw, 50%)]]99 [[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/bug-report-example.jpg?format=raw)]] 100 100 101 101 === Handling sub-tasks from a single issue === … … 103 103 Probably self explanatory: you have something that needs to be done by several different people. Split it up into sub-tasks. 104 104 105 [[Image( bug-report-example.jpg?format=raw, 50%)]]105 [[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/issue-example.jpg?format=raw)]] 106 106 107 107 === A New Feature generates bugs ===