Changes between Version 29 and Version 30 of AdvancedTicketWorkflowPlugin
- Timestamp:
- Jul 16, 2016, 8:38:28 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AdvancedTicketWorkflowPlugin
v29 v30 5 5 == Description 6 6 7 This plugin provides a number of advanced operations for customizable workflows that are similarto the operations as part of the customizeable workflow of the core system.7 This plugin provides a number of advanced operations to customise workflows. They are an enhancement to the operations as part of the customizeable workflow of the core system. 8 8 9 9 Currently provided operations are: … … 17 17 * triage 18 18 * xref 19 20 The meaning behind each of these operations is explained below. 19 21 20 22 == Bugs/Feature Requests … … 40 42 The plugin can be installed in the same way as other plugins. The simplest is to create an egg as follows: 41 43 {{{#!sh 42 python setup.py bdist_egg44 $ python setup.py bdist_egg 43 45 }}} 44 46 and copy the `.egg` file from the `dist` directory to your Trac environment's `plugins` directory. … … 50 52 }}} 51 53 52 Add the individual controller to the workflow controller list. For example, when using `set_owner_to_reporter`,`TicketWorkflowOpOwnerReporter` must be appended to the workflow controller list:54 Add the individual controller to the workflow controller list. For example, when using the operation `set_owner_to_reporter`, the `TicketWorkflowOpOwnerReporter` must be appended to the workflow controller list: 53 55 {{{#!ini 54 56 [ticket] … … 56 58 }}} 57 59 58 The controller name is unique for each workflow operation and they can be found listed in parenthes is after the operation name in the documentation section below. A controller must be added to the list for each workflow operation that is used.60 The controller name is unique for each workflow operation and they can be found listed in parentheses after the operation name in the configuration section below. A controller must be added to the list for each workflow operation that is used. 59 61 60 62 And use the operation in your custom workflow: … … 67 69 68 70 == Configuration 71 72 The following are examples of custom workflow operations together with their controller name: 69 73 70 74 * set_owner_to_reporter (!TicketWorkflowOpOwnerReporter) … … 141 145 Note that the implementation of this operation is not robust. 142 146 {{{#!ini 143 ;displays as "close as duplicate[_________]"147 ;displays as "closed as duplicate of [_________]" 144 148 dup = * -> closed 145 149 dup.name = close
