Edgewall Software

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


Ignore:
Timestamp:
Oct 29, 2009, 12:04:10 AM (14 years ago)
Author:
joost.t.hart@…
Comment:

Creation, as suggested following discussion in trac-users group.

Legend:

Unmodified
Added
Removed
Modified
  • CookBook/Configuration/Workflow

    v1 v1  
     1= Workflow Configuration (''since 0.11'') =
     2
     3TracWorkflow describes how to create your own work flow for tickets.
     4
     5This page adds some tricks of the trade to the existing documentation.
     6
     7== Multiple end states and milestone progress ==
     8
     9Trac has a more or less hard-coded ''closed'' end state. And it is the only one.
     10
     11This shows in the default RoadMap view, where milestone progress is depicted in terms of ''Closed'' and ''Active'' tickets.
     12
     13Now 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
     15But if you stop here, the RoadMap view still considers the ''rejected'' tickets as ''Active''. Your milestone will never make it.
     16
     17This is how to proceed. Add the following section to '''trac.ini''':
     18
     19{{{
     20[milestone-groups]
     21closed = closed,rejected
     22closed.order = 0
     23closed.css_class = closed
     24closed.label = closed
     25closed.overall_completion = true
     26 
     27active = *
     28active.order = 1
     29active.css_class = open
     30active.label = active
     31}}}
     32
     33The above implements the hard-coded behaviour, but adds tickets in ''rejected'' state to the ''Closed'' and completed (!) part of the progress bar.
     34
     35There is nothing much special in here (check out the description of {{{[milestone-groups]}}} in TracIni), except that for some reason the possibility of introducing a comma-separated list of states does not seem obvious. Plus the missing of a documented relationship between the two sections, I guess.
     36
     37PS: 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.