Changes between Version 3 and Version 4 of TracWorkflow
- Timestamp:
- Apr 13, 2010, 3:53:03 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracWorkflow
v3 v4 25 25 == Additional Ticket Workflows == 26 26 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.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. 28 28 29 29 Here are some [http://trac.edgewall.org/wiki/WorkFlow/Examples diagrams] of the above examples. … … 93 93 }}} 94 94 And then open up the resulting `trac.pdf` file created by the script (it will be in the same directory as the `trac.ini` file). 95 96 An online copy of the workflow parser is available at http://foss.wush.net/cgi-bin/visual-workflow.pl97 95 98 96 After 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.