Edgewall Software

Changes between Version 1 and Version 2 of CookBook/Configuration/Workflow


Ignore:
Timestamp:
Nov 23, 2009, 1:48:18 PM (14 years ago)
Author:
Christian Boos
Comment:

cross-link to TracRoadmapCustomGroups

Legend:

Unmodified
Added
Removed
Modified
  • CookBook/Configuration/Workflow

    v1 v2  
    99Trac has a more or less hard-coded ''closed'' end state. And it is the only one.
    1010
    11 This shows in the default RoadMap view, where milestone progress is depicted in terms of ''Closed'' and ''Active'' tickets.
     11This shows in the default [TracRoadmap roadmap] view, where milestone progress is depicted in terms of ''Closed'' and ''Active'' tickets.
    1212
    1313Now 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.
    1414
    15 But if you stop here, the RoadMap view still considers the ''rejected'' tickets as ''Active''. Your milestone will never make it.
     15But if you stop here, the roadmap view still considers the ''rejected'' tickets as ''Active''. Your milestone will never make it.
    1616
    1717This is how to proceed. Add the following section to '''trac.ini''':
     
    3636
    3737PS: 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
     39See also: TracRoadmapCustomGroups