| | 94 | == Example: Adding optional Testing with Workflow == |
| | 95 | |
| | 96 | By adding the following to your [ticket-workflow] section of trac.ini you get optional testing. When the ticket is in new, accepted or needs_work status you can choose to submit it for testing. When it's in the testing status the user gets the option to reject it and send it back to needs_work, or pass the testing and send it along to closed. If they accept it then it gets automatically marked as closed and the resolution is set to fixed. Since all the old work flow remains, a ticket can skip this entire section. |
| | 97 | |
| | 98 | {{{ |
| | 99 | testing = new,accepted,needs_work -> testing |
| | 100 | testing.name = Submit to reporter for testing |
| | 101 | testing.permissions = TICKET_MODIFY |
| | 102 | |
| | 103 | reject = testing -> needs_work |
| | 104 | reject.name = Failed testing, return to developer |
| | 105 | |
| | 106 | pass = testing -> closed |
| | 107 | pass.name = Passes Testing |
| | 108 | pass.operations = set_resolution |
| | 109 | pass.set_resolution = fixed |
| | 110 | }}} |
| | 111 | |
| | 112 | == Example: Limit the resolution options for a new ticket == |
| | 113 | |
| | 114 | The above resolve_new operation allows you to set the possible resolutions for a new ticket. By modifying the existing resolve action and removing the new status from before the `->` we then get two resolve actions. One with limited resolutions for new tickets, and then the regular one once a ticket is accepted. |
| | 115 | |
| | 116 | {{{ |
| | 117 | resolve_new = new -> closed |
| | 118 | resolve_new.name = resolve |
| | 119 | resolve_new.operations = set_resolution |
| | 120 | resolve_new.permissions = TICKET_MODIFY |
| | 121 | resolve_new.set_resolution = invalid,wontfix,duplicate |
| | 122 | |
| | 123 | resolve = assigned,accepted,reopened -> closed |
| | 124 | resolve.operations = set_resolution |
| | 125 | resolve.permissions = TICKET_MODIFY |
| | 126 | }}} |
| | 127 | |
| | 134 | == some ideas for next steps == |
| | 135 | |
| | 136 | 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. |
| | 137 | |
| | 138 | If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket. |
| | 139 | |
| | 140 | * the "operation" could be on the nodes, possible operations are: |
| | 141 | * '''preops''': automatic, before entering the state/activity |
| | 142 | * '''postops''': automatic, when leaving the state/activity |
| | 143 | * '''actions''': can be chosen by the owner in the list at the bottom, and/or drop-down/pop-up together with the default actions of leaving the node on one of the arrows. |
| | 144 | This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement. |
| | 145 | |
| | 146 | * operations could be anything: sum up the time used for the activity, or just write some statistical fields like |
| | 147 | A workflow plugin can add an arbitrary workflow operation, so this is already possible. |
| | 148 | |
| | 149 | * set_actor should be an operation allowing to set the owner, e.g. as a "preop": |
| | 150 | * either to a role, a person |
| | 151 | * entered fix at define time, or at run time, e.g. out of a field, or select. |
| | 152 | This is either duplicating the existing `set_owner` operation, or needs to be clarified. |
| | 153 | |
| | 154 | * Actions should be selectable based on the ticket type (different Workflows for different tickets) |
| | 155 | This is becoming a frequent request, with clear usecases. The closest the current implementation will allow is to have a plugin provide a `triage` action that sets the next state based on the ticket type, so a `new` ticket would move to `new_task`, `new_defect`, etc., and the workflow graph would separate at that point. |
