Changes between Version 1 and Version 2 of ChildTicketsPlugin/Examples


Ignore:
Timestamp:
Jan 5, 2012, 9:44:35 PM (3 years ago)
Author:
walnut
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ChildTicketsPlugin/Examples

    v1 v2  
    77In 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 ...
    88
    9 [[Image(bug-report-example.jpg)]]
     9[[Image(wiki:ChildTicketsPlugin:bug-report-example.jpg)]]
    1010
    1111=== Handling sub-tasks from a single issue ===
     
    1313Probably self explanatory: you have something that needs to be done by several different people. Split it up into sub-tasks.
    1414
    15 [[Image(issue-example.jpg)]]
     15[[Image(wiki:ChildTicketsPlugin:issue-example.jpg)]]
    1616
    1717=== A New Feature generates bugs ===
     
    2323If you are using the above option, the available child types will be rendered as individual buttons.
    2424
    25 [[Image(MultipleChildType.png)]]
     25[[Image(wiki:ChildTicketsPlugin:MultipleChildType.png)]]
    2626
    2727=== Creating a Progress Bar for Child Tickets ===
     
    3535Then the following will appear in the ticket description:
    3636
    37 [[Image(progmeter_ticket.png)]]
     37[[Image(wiki:ChildTicketsPlugin:progmeter_ticket.png)]]