Edgewall Software

Changes between Version 68 and Version 69 of TracWorkflow


Ignore:
Timestamp:
Mar 21, 2017, 12:02:24 AM (8 months ago)
Author:
Ryan J Ollos
Comment:

Add some section so we can link here.

Legend:

Unmodified
Added
Removed
Modified
  • TracWorkflow

    v68 v69  
    104104If not specified for an action, `.default` is 0. The value may be negative.
    105105
     106There is one hard-coded constraint to the workflow: tickets are expected to have a `closed` state. The default reports/queries treat any state other than `closed` as an open state.
     107
     108=== Ticket Create Action
     109
    106110The ticket create actions are specified by a transition from the special `<none>` state. At least one create action must be available to the user in order for tickets to be created. The create actions defined in the default workflow are:
    107111{{{#!ini
     
    115119}}}
    116120
    117 
    118 There is one hard-coded constraints to the workflow: tickets are expected to have a `closed` state. The default reports/queries treat any state other than `closed` as an open state.
     121=== Ticket Reset Action
    119122
    120123The 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: