Changes between Version 10 and Version 11 of ChildTicketsPlugin

Timestamp:

Feb 12, 2011, 11:15:08 AM (13 years ago)

Author:

Mark Ryan

Comment:

--

ChildTicketsPlugin

@@ -101 +101 @@
 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 ... 
 
-[[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/bug-report-example.jpg?format=raw)]]
+[[Image(bug-report-example.jpg)]]
 
 === Handling sub-tasks from a single issue ===
@@ -107 +107 @@
 Probably self explanatory: you have something that needs to be done by several different people. Split it up into sub-tasks.
 
-[[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/issue-example.jpg?format=raw)]]
+[[Image(issue-example.jpg)]]
 
 === A New Feature generates bugs ===
@@ -117 +117 @@
 If you are using the above option, the available child types will be rendered as individual buttons.
 
-[[Image(http://trac-hacks.org/attachment/wiki/ChildTicketsPlugin/perTypeButtons.png?format=raw)]]
+[[Image(perTypeButtons.png)]]
 
 == Recent Changes ==