Changes between Version 2 and Version 3 of TracWorkflow
- Timestamp:
- Dec 16, 2007, 9:52:56 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracWorkflow
v2 v3 25 25 == Additional Ticket Workflows == 26 26 27 There are several example workflows provided in the Trac source tree; look in `contrib/workflow` for `.ini` config sections. One of those may be a good match for what you want. 27 There are several example workflows provided in the Trac source tree; look in `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 == Basic Ticket Workflow Customization == … … 49 49 - set_resolution -- Sets the resolution to the selected value. 50 50 - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value. 51 {{{ 52 Example: 53 54 resolve_new = new -> closed 55 resolve_new.name = resolve 56 resolve_new.operations = set_resolution 57 resolve_new.permissions = TICKET_MODIFY 58 resolve_new.set_resolution = invalid,wontfix 59 }}} 51 60 - leave_status -- Displays "leave as <current status>" and makes no change to the ticket. 52 61 '''Note:''' Specifying conflicting operations (such as `set_owner` and `del_owner`) has unspecified results. … … 74 83 While creating or modifying a ticket workfow, `contrib/workflow/workflow_parser.py` may be useful. It can create `.dot` files that [http://www.graphviz.org GraphViz] understands to provide a visual description of the workflow. 75 84 85 This can be done as follows (your install path may be different). 86 {{{ 87 cd /var/local/trac_devel/contrib/workflow/ 88 sudo ./showworkflow /srv/trac/PlannerSuite/conf/trac.ini 89 }}} 90 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). 91 92 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. 93 76 94 == Advanced Ticket Workflow Customization == 77 95 78 If the customization above is not extensive enough for your needs, you can extend the workflow using plugins. These plugins can provide additional operations for the workflow (like code_review), or implement side-effects for an action (such as triggering a build) . Look at `sample-plugins/workflow` for a few simple examples to get started.96 If the customization above is not extensive enough for your needs, you can extend the workflow using plugins. These plugins can provide additional operations for the workflow (like code_review), or implement side-effects for an action (such as triggering a build) that may not be merely simple state changes. Look at `sample-plugins/workflow` for a few simple examples to get started. 79 97 80 98 But if even that is not enough, you can disable the !ConfigurableTicketWorkflow component and create a plugin that completely replaces it. 99