Changes between Version 3 and Version 4 of TracWorkflow
- Timestamp:
- 12/08/13 22:22:58 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracWorkflow
v3 v4 52 52 - del_resolution -- Clears the resolution field 53 53 - set_resolution -- Sets the resolution to the selected value. 54 - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value. 55 {{{ 56 Example: 57 54 - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value. Example: 55 {{{ 58 56 resolve_new = new -> closed 59 57 resolve_new.name = resolve … … 61 59 resolve_new.permissions = TICKET_MODIFY 62 60 resolve_new.set_resolution = invalid,wontfix 63 }}}61 }}} 64 62 - leave_status -- Displays "leave as <current status>" and makes no change to the ticket. 65 63 '''Note:''' Specifying conflicting operations (such as `set_owner` and `del_owner`) has unspecified results. … … 118 116 === How to combine the `tracopt.ticket.commit_updater` with the testing workflow === 119 117 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.118 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. 121 119 122 120 By default it reacts on some keywords found in changeset message logs like ''close'', ''fix'' etc. and performs the corresponding workflow action. … … 124 122 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 123 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.124 Have a look at the [[trac:wiki: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. 127 125 128 126 == Example: Add simple optional generic review state == … … 165 163 leave.default = 1 166 164 leave.operations = leave_status 167 reassign = new,assigned, reopened -> new165 reassign = new,assigned,accepted,reopened -> assigned 168 166 reassign.operations = set_owner 169 167 reassign.permissions = TICKET_MODIFY … … 211 209 == some ideas for next steps == 212 210 213 New enhancement ideas for the workflow system should be filed as enhancement tickets against the `ticket system` component. If desired, add a single-line link to that ticket here. Also look at the [ th:wiki:AdvancedTicketWorkflowPlugin] as it provides experimental operations.211 New enhancement ideas for the workflow system should be filed as enhancement tickets against the `ticket system` component. If desired, add a single-line link to that ticket here. Also look at the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin] as it provides experimental operations. 214 212 215 213 If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket. … … 230 228 231 229 * Actions should be selectable based on the ticket type (different Workflows for different tickets) 232 ''Look into the [th:wiki:AdvancedTicketWorkflowPlugin]'s `triage` operation.'' 233 230 ''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s `triage` operation.'' 231 232 * I'd wish to have an option to perform automatic status changes. In my case, I do not want to start with "new", but with "assigned". So tickets in state "new" should automatically go into state "assigned". Or is there already a way to do this and I just missed it? 233 ''Have a look at [http://trac-hacks.org/wiki/TicketCreationStatusPlugin TicketCreationStatusPlugin] and [http://trac-hacks.org/wiki/TicketConditionalCreationStatusPlugin TicketConditionalCreationStatusPlugin]'' 234 235 * I added a 'testing' state. A tester can close the ticket or reject it. I'd like the transition from testing to rejected to set the owner to the person that put the ticket in 'testing'. The [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin] is close with set_owner_to_field, but we need something like set_field_to_owner. 236 237 * I'd like to track the time a ticket is in each state, adding up 'disjoints' intervals in the same state.
