close
Warning:
Can't synchronize with repository "(default)" (Unsupported version control system "darcs": Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information.
- Timestamp:
-
2011-11-18 01:44:17 (13 years ago)
- Author:
-
trac
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v1
|
v2
|
|
115 | 115 | pass.set_resolution = fixed |
116 | 116 | }}} |
| 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. |
117 | 127 | |
118 | 128 | == Example: Add simple optional generic review state == |
… |
… |
|
221 | 231 | * Actions should be selectable based on the ticket type (different Workflows for different tickets) |
222 | 232 | ''Look into the [th:wiki:AdvancedTicketWorkflowPlugin]'s `triage` operation.'' |
| 233 | |