Changes between Version 13 and Version 14 of TracWorkflow
- Timestamp:
- May 22, 2020, 2:41:47 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracWorkflow
v13 v14 56 56 == Additional Ticket Workflows 57 57 58 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.58 There are example workflows provided in the Trac source tree, see [trac:source:branches/1.0-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. 59 59 60 60 Here are some [trac:WorkFlow/Examples diagrams] of the above examples. … … 172 172 === How to combine the `tracopt.ticket.commit_updater` with the testing workflow 173 173 174 The [[trac: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.174 The [[trac:source:branches/1.0-stable/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. 175 175 176 176 By default it reacts on some keywords found in changeset message logs like ''close'', ''fix'' etc. and performs the corresponding workflow action. … … 205 205 reassign_reviewing = reviewing -> * 206 206 reassign_reviewing.name = reassign review 207 reassign_reviewing.operations = set_owner 207 reassign_reviewing.operations = set_owner, leave_status 208 208 reassign_reviewing.permissions = TICKET_MODIFY 209 209 }}} … … 232 232 review.permissions = TICKET_MODIFY 233 233 reassign_reviewing = reviewing -> * 234 reassign_reviewing.operations = set_owner 234 reassign_reviewing.operations = set_owner, leave_status 235 235 reassign_reviewing.name = reassign review 236 236 reassign_reviewing.permissions = TICKET_MODIFY … … 255 255 == Advanced Ticket Workflow Customization 256 256 257 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.257 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.0-stable/sample-plugins/workflow sample-plugins/workflow] for a few examples to get started. 258 258 259 259 But if even that is not enough, you can disable the !ConfigurableTicketWorkflow component and create a plugin that completely replaces it.