Changes between Version 5 and Version 6 of 1.1/TracWorkflow
- Timestamp:
- Dec 5, 2014, 2:45:18 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
1.1/TracWorkflow
v5 v6 2 2 [[TracGuideToc]] 3 3 4 The Trac issue database provides a configurable workflow.4 The Trac ticket workflow is configurable. 5 5 6 6 == The Default Ticket Workflow == … … 14 14 leave.operations = leave_status 15 15 leave.default = 1 16 17 create = <none> -> new 18 create.default = 1 19 20 create_and_assign = <none> -> assigned 21 create_and_assign.label = assign 22 create_and_assign.permissions = TICKET_MODIFY 23 create_and_assign.operations = may_set_owner 24 16 25 accept = new,assigned,accepted,reopened -> accepted 17 26 accept.permissions = TICKET_MODIFY 18 27 accept.operations = set_owner_to_self 28 19 29 resolve = new,assigned,accepted,reopened -> closed 20 30 resolve.permissions = TICKET_MODIFY 21 31 resolve.operations = set_resolution 32 22 33 reassign = new,assigned,accepted,reopened -> assigned 23 34 reassign.permissions = TICKET_MODIFY 24 35 reassign.operations = set_owner 36 25 37 reopen = closed -> reopened 26 38 reopen.permissions = TICKET_CREATE … … 36 48 == Basic Ticket Workflow Customization == 37 49 38 Note: Ticket "statuses" or "states" are not separately defined. The states a ticket can be inare automatically generated by the transitions defined in a workflow. Therefore, creating a new ticket state simply requires defining a state transition in the workflow that starts or ends with that state.50 Note: Ticket "statuses" or "states" are not separately defined. The ticket states are automatically generated by the transitions defined in a workflow. Therefore, creating a new ticket state simply requires defining a state transition in the workflow that starts or ends with that state. 39 51 40 52 Create a `[ticket-workflow]` section in `trac.ini`. … … 87 99 If not specified for an action, `.default` is 0. The value may be negative. 88 100 101 The 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: 102 {{{#!ini 103 create = <none> -> new 104 create.default = 1 105 106 create_and_assign = <none> -> assigned 107 create_and_assign.label = assign 108 create_and_assign.permissions = TICKET_MODIFY 109 create_and_assign.operations = may_set_owner 110 }}} 111 112 89 113 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. 90 114 … … 165 189 {{{ 166 190 [ticket-workflow] 191 create = <none> -> new 192 create.default = 1 193 create_and_assign = <none> -> assigned 194 create_and_assign.label = assign 195 create_and_assign.permissions = TICKET_MODIFY 196 create_and_assign.operations = may_set_owner 167 197 accept = new,reviewing -> assigned 168 198 accept.operations = set_owner_to_self