Changes between Version 19 and Version 20 of TracWorkflow
- Timestamp:
- May 8, 2008, 4:46:45 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracWorkflow
v19 v20 134 134 == some ideas for next steps == 135 135 136 New enhancement ideas for the workflow system should be filed as enhancement tickets against the `ticket system` component. If desired, add a single-line link to that ticket here. 136 New enhancement ideas for the workflow system should be filed as enhancement tickets against the `ticket system` component. If desired, add a single-line link to that ticket here. Also look at the [th:wiki:AdvancedTicketWorkflowPlugin] as it provides experimental operations. 137 137 138 138 If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket. … … 142 142 * '''postops''': automatic, when leaving the state/activity 143 143 * '''actions''': can be chosen by the owner in the list at the bottom, and/or drop-down/pop-up together with the default actions of leaving the node on one of the arrows. 144 This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement. 144 ''This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement.'' 145 145 146 146 * operations could be anything: sum up the time used for the activity, or just write some statistical fields like 147 A workflow plugin can add an arbitrary workflow operation, so this is already possible. 147 ''A workflow plugin can add an arbitrary workflow operation, so this is already possible.'' 148 148 149 149 * set_actor should be an operation allowing to set the owner, e.g. as a "preop": 150 150 * either to a role, a person 151 151 * entered fix at define time, or at run time, e.g. out of a field, or select. 152 This is either duplicating the existing `set_owner` operation, or needs to be clarified. 152 ''This is either duplicating the existing `set_owner` operation, or needs to be clarified.'' 153 153 154 154 * Actions should be selectable based on the ticket type (different Workflows for different tickets) 155 This is becoming a frequent request, with clear usecases. The closest the current implementation will allow is to have a plugin provide a `triage` action that sets the next state based on the ticket type, so a `new` ticket would move to `new_task`, `new_defect`, etc., and the workflow graph would separate at that point. 155 ''This is becoming a frequent request, with clear usecases. The closest the current implementation will allow is to have a plugin provide a `triage` action that sets the next state based on the ticket type, so a `new` ticket would move to `new_task`, `new_defect`, etc., and the workflow graph would separate at that point.''