| 117 | |
| 118 | The special `_reset` action is added by default for tickets that are in states that are no longer defined. This allows tickets to be individually "repaired" after the workflow is changed, although it's recommended that the administrator perform the action by batch modifying the affected tickets. By default the `_reset` action is available to users with the `TICKET_ADMIN` permission and reset tickets are put in the //new// state. The default `_reset` action is equivalent to the following `[ticket-workflow]` action definition: |
| 119 | {{{#!ini |
| 120 | _reset = -> new |
| 121 | _reset.name = reset |
| 122 | _reset.operations = reset_workflow |
| 123 | _reset.permissions = TICKET_ADMIN |
| 124 | _reset.default = 0 |
| 125 | }}} |
| 126 | |
| 127 | Since [trac:milestone:1.0.3] the `_reset` action can be customized by treating the above definition of `_reset` as implicit to the `[ticket-workflow]` section and modifying the workflow attributes as desired. For example, to allow anyone with `TICKET_MODIFY` to perform the `_reset` action, only the following would be needed: |
| 128 | {{{#!ini |
| 129 | _reset.permissions = TICKET_MODIFY |
| 130 | }}} |