Changes between Version 60 and Version 64 of TracWorkflow

Timestamp:

(multiple changes)

Author:

(multiple changes)

Comment:

(multiple changes)

TracWorkflow

@@ -1 +1 @@
 = The Trac Ticket Workflow System =
+[[PageOutline(2-5,Contents,pullout)]]
 [[TracGuideToc]]
-
 The Trac ticket system provides a configurable workflow.
 
@@ -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 redefining the implicit action. For example, to allow anyone with `TICKET_MODIFY` to perform the `_reset` action, the workflow action would need to be defined:
+{{{#!ini
+_reset = -> new
+_reset.name = reset
+_reset.operations = reset_workflow
+_reset.permissions = TICKET_MODIFY
+_reset.default = 0
+}}}
+
+== Workflow Visualization
 
 Workflows can be visualized by rendering them on the wiki using the [WikiMacros#Workflow-macro Workflow macro].