Changes between Version 5 and Version 6 of TracWorkflow


Ignore:
Timestamp:
Apr 6, 2012, 4:33:29 PM (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracWorkflow

    v5 v6  
    2525== Additional Ticket Workflows ==
    2626
    27 There are several example workflows provided in the Trac source tree; look in [trac:source:trunk/contrib/workflow contrib/workflow] for `.ini` config sections.  One of those may be a good match for what you want. They can be pasted into the `[ticket-workflow]` section of your `trac.ini` file. However if you have existing tickets then there may be issues if those tickets have states that are not in the new workflow.
     27There are several example workflows provided in the Trac source tree; look in [trac:source:trunk/contrib/workflow contrib/workflow] for `.ini` config sections.  One of those may be a good match for what you want. They can be pasted into the `[ticket-workflow]` section of your `trac.ini` file.
    2828
    2929Here are some [http://trac.edgewall.org/wiki/WorkFlow/Examples diagrams] of the above examples.
     
    9494And then open up the resulting `trac.pdf` file created by the script (it will be in the same directory as the `trac.ini` file).
    9595
    96 An online copy of the workflow parser is available at http://foss.wush.net/cgi-bin/visual-workflow.pl
    97 
    9896After you have changed a workflow, you need to restart apache for the changes to take effect. This is important, because the changes will still show up when you run your script, but all the old workflow steps will still be there until the server is restarted.
    9997
     
    115113pass.set_resolution = fixed
    116114}}}
    117 
    118 === How to combine the `tracopt.ticket.commit_updater` with the testing workflow ===
    119 
    120 The [[source:trunk/tracopt/ticket/commit_updater.py|tracopt.ticket.commit_updater]] is the optional component that [[TracRepositoryAdmin#trac-post-commit-hook|replaces the old trac-post-commit-hook]], in Trac 0.12.
    121 
    122 By default it reacts on some keywords found in changeset message logs like ''close'', ''fix'' etc. and performs the corresponding workflow action.
    123 
    124 If you have a more complex workflow, like the testing stage described above and you want the ''closes'' keyword to move the ticket to the ''testing'' status instead of the ''closed'' status, you need to adapt the code a bit.
    125 
    126 Have a look at the [[0.11/TracWorkflow#How-ToCombineSVNtrac-post-commit-hookWithTestWorkflow|Trac 0.11 recipe]] for the `trac-post-commit-hook`, this will give you some ideas about how to modify the component.
    127115
    128116== Example: Add simple optional generic review state ==