Changes between Version 10 and Version 11 of ChildTicketsPlugin


Ignore:
Timestamp:
Feb 12, 2011, 12:15:08 PM (4 years ago)
Author:
walnut
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ChildTicketsPlugin

    v10 v11  
    101101In 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 ...
    102102
    103 [[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/bug-report-example.jpg?format=raw)]]
     103[[Image(bug-report-example.jpg)]]
    104104
    105105=== Handling sub-tasks from a single issue ===
     
    107107Probably self explanatory: you have something that needs to be done by several different people. Split it up into sub-tasks.
    108108
    109 [[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/issue-example.jpg?format=raw)]]
     109[[Image(issue-example.jpg)]]
    110110
    111111=== A New Feature generates bugs ===
     
    117117If you are using the above option, the available child types will be rendered as individual buttons.
    118118
    119 [[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/perTypeButtons.png?format=raw)]]
     119[[Image(perTypeButtons.png)]]
    120120
    121121== Recent Changes ==