Edgewall Software

Changes between Version 4 and Version 5 of CookBook/Configuration/Workflow


Ignore:
Timestamp:
Feb 1, 2015, 11:46:36 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • CookBook/Configuration/Workflow

    v4 v5  
    1 = Workflow Configuration (''since 0.11'') =
     1= Workflow Configuration
    22
    33TracWorkflow describes how to create your own workflow for tickets.
    … …  
    55This page adds some tricks of the trade to the existing documentation.
    66
    7 == Multiple end states and milestone progress ==
     7== Multiple end states and milestone progress
    88
    9 Trac has a more or less hard-coded ''closed'' end state. And it is the only one.
     9In Trac a ticket has a single end state, called ''Closed''. This shows in the default [TracRoadmap roadmap] view, where milestone progress is depicted in terms of ''Closed'' and ''Active'' tickets.
    1010
    11 This shows in the default [TracRoadmap roadmap] view, where milestone progress is depicted in terms of ''Closed'' and ''Active'' tickets.
    12 
    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 teaches you how to create these states and how to add the desired transitions.
     11Now suppose you need to differentiate between problems that actually took effort before reaching ''Closed'' state, and problems that were ''rejected'' for some reason. TracWorkflow explains how to create these states and how to add the desired transitions.
    1412
    1513But if you stop here, the roadmap view still considers the ''rejected'' tickets as ''Active''. Your milestone will never make it.
    1614
    17 This is how to proceed. Add the following section to '''trac.ini''':
     15To fix this, add the following section to '''trac.ini''':
    1816
    1917{{{#!ini
    … …  
    3129}}}
    3230
    33 The above implements the hard-coded behaviour, but adds tickets in ''rejected'' state to the ''Closed'' and completed (!) part of the progress bar.
     31The above implements the hard-coded behaviour, but adds tickets in ''rejected'' state to the ''Closed'' and completed part of the progress bar.
    3432
    35 There is nothing much special in here (check out the description of [TracIni#milestone-groups-section 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.
     33Within Trac the word `closed` has many meanings and occurrences: 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.
    3634
    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
     35See also: TracRoadmapCustomGroups, [TracIni#milestone-groups-section milestone-groups] in TracIni