Changes between Version 61 and Version 62 of TracWorkflow

Timestamp:

Nov 27, 2014, 2:30:47 AM (9 years ago)

Author:

Ryan J Ollos

Comment:

Document changes to the implicit _reset action in #11850.

TracWorkflow

@@ -93 +93 @@
 }}}
 - **leave_status** -- Displays "leave as <current status>" and makes no change to the ticket.
+- **reset_workflow** -- Resets the status of tickets that are in states no longer defined.
 '''Note:''' Specifying conflicting operations (such as `set_owner` and `del_owner`) has unspecified results.
 
@@ -114 +115 @@
 
 There are a couple of hard-coded constraints to the workflow.  In particular, tickets are created with status `new`, and tickets are expected to have a `closed` state.  Further, the default reports/queries treat any state other than `closed` as an open state.
+
+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:
+{{{#!ini
+_reset = -> new
+_reset.name = reset
+_reset.operations = reset_workflow
+_reset.permissions = TICKET_ADMIN
+_reset.default = 0
+}}}
+
+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:
+{{{#!ini
+_reset.permissions = TICKET_MODIFY
+}}}
 
 == Workflow Visualization