Changes between Version 5 and Version 6 of TracWorkflow
- Timestamp:
- May 21, 2019, 4:35:17 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracWorkflow
v5 v6 7 7 == The Default Ticket Workflow 8 8 9 When a new environment is created, a default workflow is configured in your trac.ini. This workflow is the basic workflow, as specified in [trac:source: /trunk/trac/ticket/workflows/basic-workflow.ini basic-workflow.ini]:9 When a new environment is created, a default workflow is configured in your trac.ini. This workflow is the basic workflow, as specified in [trac:source:branches/1.2-stable/trac/ticket/workflows/basic-workflow.ini basic-workflow.ini]: 10 10 11 11 {{{#!Workflow width=700 height=300 … … 41 41 == Additional Ticket Workflows 42 42 43 There are example workflows provided in the Trac source tree, see [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.43 There are example workflows provided in the Trac source tree, see [trac:source:branches/1.2-stable/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. 44 44 45 45 Here are some [trac:WorkFlow/Examples diagrams] of the above examples. … … 72 72 - **del_resolution** -- Clears the resolution field. 73 73 - **set_resolution** -- Sets the resolution to the selected value. 74 - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value. Example:74 - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value. The resolution(s) specified in this attribute must be defined in the database. Example: 75 75 {{{#!ini 76 76 resolve_new = new -> closed … … 237 237 == Advanced Ticket Workflow Customization 238 238 239 If the customizations above do not meet your needs, you can extend the workflow with plugins. 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 [trac:source:trunk/sample-plugins/workflow sample-plugins/workflow] for a few examples to get started.239 If the customizations above do not meet your needs, you can extend the workflow with plugins. 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 [trac:source:branches/1.2-stable/sample-plugins/workflow sample-plugins/workflow] for a few examples to get started. 240 240 241 241 But if even that is not enough, you can disable the !ConfigurableTicketWorkflow component and create a plugin that completely replaces it. See also the [https://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin], which provides additional operations.