| 7 | | === Environments upgraded from 0.10 === |
| 8 | | When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. |
| 9 | | The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10. |
| 10 | | |
| 11 | | Graphically, that looks like this: |
| 12 | | |
| 13 | | {{{#!Workflow width=500 height=240 |
| 14 | | leave = * -> * |
| 15 | | leave.operations = leave_status |
| 16 | | leave.default = 1 |
| 17 | | accept = new -> assigned |
| 18 | | accept.permissions = TICKET_MODIFY |
| 19 | | accept.operations = set_owner_to_self |
| 20 | | resolve = new,assigned,reopened -> closed |
| 21 | | resolve.permissions = TICKET_MODIFY |
| 22 | | resolve.operations = set_resolution |
| 23 | | reassign = new,assigned,reopened -> new |
| 24 | | reassign.permissions = TICKET_MODIFY |
| 25 | | reassign.operations = set_owner |
| 26 | | reopen = closed -> reopened |
| 27 | | reopen.permissions = TICKET_CREATE |
| 28 | | reopen.operations = del_resolution |
| 29 | | }}} |
| 30 | | |
| 31 | | 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? |
| 32 | | 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. |
| 33 | | |
| 34 | | === Environments created with 0.11 === |
| 35 | | When a new environment is created, a default workflow is configured in your trac.ini. This workflow is the basic workflow (described in `basic-workflow.ini`), which is somewhat different from the workflow of the 0.10 releases. |
| | 7 | |
| | 8 | When a new environment is created, a default workflow is configured in your trac.ini. This workflow is the basic workflow, described in `basic-workflow.ini`. |
