Changes between Version 4 and Version 5 of TracIdeas/TracWorkflow
- Timestamp:
- Jan 15, 2015, 10:45:33 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracIdeas/TracWorkflow
v4 v5 22 22 == Workflow Actions 23 23 24 //(this content was copied from the TracWorkflow page and should be cleaned up)//25 26 24 If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket. 27 25 28 * the "operation" could be on the nodes, possible operations are: 29 * '''preops''': automatic, before entering the state/activity 30 * '''postops''': automatic, when leaving the state/activity 31 * '''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. 32 ''This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement.'' 26 * the "operation" could be on the nodes, possible operations are: 27 * '''preops''': automatic, before entering the state/activity 28 * '''postops''': automatic, when leaving the state/activity 29 * '''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. 30 31 ''This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement.'' 33 32 34 * operations could be anything: sum up the time used for the activity, or just write some statistical fields like 35 ''A workflow plugin can add an arbitrary workflow operation, so this is already possible.'' 33 * operations could be anything: sum up the time used for the activity, or just write some statistical fields like 36 34 37 * set_actor should be an operation allowing to set the owner, e.g. as a "preop": 35 ''A workflow plugin can add an arbitrary workflow operation, so this is already possible.'' 36 37 * set_actor should be an operation allowing to set the owner, e.g. as a "preop": 38 38 * either to a role, a person 39 39 * entered fix at define time, or at run time, e.g. out of a field, or select. 40 ''This is either duplicating the existing `set_owner` operation, or needs to be clarified.'' 40 41 ''This is either duplicating the existing `set_owner` operation, or needs to be clarified.'' 41 42 42 43 * Actions should be selectable based on the ticket type (different Workflows for different tickets) 43 ''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s `triage` operation.'' 44 45 ''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s `triage` operation.'' 44 46 45 * I added a 'testing' state. A tester can close the ticket or reject it. I'd like the transition from testing to rejected to set the owner to the person that put the ticket in 'testing'. The [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPluginAdvancedTicketWorkflowPlugin] is close with set_owner_to_field, but we need something like set_field_to_owner.47 * I added a 'testing' state. A tester can close the ticket or reject it. I'd like the transition from testing to rejected to set the owner to the person that put the ticket in 'testing'. The [th:AdvancedTicketWorkflowPlugin] is close with set_owner_to_field, but we need something like set_field_to_owner. 46 48 47 ''See for example [wiki:TracDev/PluginDevelopment/ExtensionPoints/trac.ticket.api.ITicketChangeListener ITicketChangeListener]. This will allow you to write a plugin that will suit your needs.''49 ''See for example [wiki:TracDev/PluginDevelopment/ExtensionPoints/trac.ticket.api.ITicketChangeListener ITicketChangeListener]. This will allow you to write a plugin that will suit your needs.'' 48 50 49 51 * I'd like to track the time a ticket is in each state, adding up 'disjoints' intervals in the same state. 50 52 51 ''You could do a query on the ticket table and the ticket changes table and find out transitions between individual states and the time the ticket had been in each of the available states.''53 ''You could do a query on the ticket table and the ticket changes table and find out transitions between individual states and the time the ticket had been in each of the available states.'' 52 54 53 55 54 56 == Workflow attributes 55 57 56 * `restrict_owner` field for `set_owner` and `may_set_owner` operations that overrides the global `[ticket] restrict_owner` setting.58 * `restrict_owner` field for `set_owner` and `may_set_owner` operations that overrides, or replaces, the global `[ticket] restrict_owner` setting. 57 59 58 60 ----