Changes between Version 1 and Version 2 of CookBook/Configuration/Workflow
- Timestamp:
- Nov 23, 2009, 1:48:18 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CookBook/Configuration/Workflow
v1 v2 9 9 Trac has a more or less hard-coded ''closed'' end state. And it is the only one. 10 10 11 This shows in the default RoadMapview, where milestone progress is depicted in terms of ''Closed'' and ''Active'' tickets.11 This shows in the default [TracRoadmap roadmap] view, where milestone progress is depicted in terms of ''Closed'' and ''Active'' tickets. 12 12 13 13 Now suppose you need to differentiate between problems that actually took effort before reaching ''closed'' state, and problems that were ''rejected'' for some reason. TracWorkflow learns you how to create these states and how to add the desired transitions. 14 14 15 But if you stop here, the RoadMap view still considers the ''rejected'' tickets as ''Active''. Your milestone will never make it.15 But if you stop here, the roadmap view still considers the ''rejected'' tickets as ''Active''. Your milestone will never make it. 16 16 17 17 This is how to proceed. Add the following section to '''trac.ini''': … … 36 36 37 37 PS: Note the heavy overloading of the word {{{closed}}} above; it denotes the name of a group, a ticket state, a css class (creating the green color in the leftmost (0) part of the progress bar) and a text label. 38 39 See also: TracRoadmapCustomGroups