| 156 | ===== New Default Configurable Workflow |
| 157 | |
| 158 | When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10. |
| 159 | |
| 160 | Graphically, that looks like this: |
| 161 | |
| 162 | {{{#!Workflow width=500 height=240 |
| 163 | leave = * -> * |
| 164 | leave.operations = leave_status |
| 165 | leave.default = 1 |
| 166 | accept = new -> assigned |
| 167 | accept.permissions = TICKET_MODIFY |
| 168 | accept.operations = set_owner_to_self |
| 169 | resolve = new,assigned,reopened -> closed |
| 170 | resolve.permissions = TICKET_MODIFY |
| 171 | resolve.operations = set_resolution |
| 172 | reassign = new,assigned,reopened -> new |
| 173 | reassign.permissions = TICKET_MODIFY |
| 174 | reassign.operations = set_owner |
| 175 | reopen = closed -> reopened |
| 176 | reopen.permissions = TICKET_CREATE |
| 177 | reopen.operations = del_resolution |
| 178 | }}} |
| 179 | |
| 180 | There are some significant "warts" in this; such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. Perfectly obvious, right? |
| 181 | So you will probably want to migrate to "basic" workflow; [trac:source:trunk/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow. |
| 182 | |