| 23 | | == Other glitches |
| | 23 | == Workflow Actions |
| | 24 | |
| | 25 | //(this content was copied from the TracWorkflow page and should be cleaned up)// |
| | 26 | |
| | 27 | If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket. |
| | 28 | |
| | 29 | * the "operation" could be on the nodes, possible operations are: |
| | 30 | * '''preops''': automatic, before entering the state/activity |
| | 31 | * '''postops''': automatic, when leaving the state/activity |
| | 32 | * '''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. |
| | 33 | ''This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement.'' |
| | 34 | |
| | 35 | * operations could be anything: sum up the time used for the activity, or just write some statistical fields like |
| | 36 | ''A workflow plugin can add an arbitrary workflow operation, so this is already possible.'' |
| | 37 | |
| | 38 | * set_actor should be an operation allowing to set the owner, e.g. as a "preop": |
| | 39 | * either to a role, a person |
| | 40 | * entered fix at define time, or at run time, e.g. out of a field, or select. |
| | 41 | ''This is either duplicating the existing `set_owner` operation, or needs to be clarified.'' |
| | 42 | |
| | 43 | * Actions should be selectable based on the ticket type (different Workflows for different tickets) |
| | 44 | ''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s `triage` operation.'' |
| | 45 | |
| | 46 | * I'd wish to have an option to perform automatic status changes. In my case, I do not want to start with "new", but with "assigned". So tickets in state "new" should automatically go into state "assigned". Or is there already a way to do this and I just missed it? |
| | 47 | ''Have a look at [http://trac-hacks.org/wiki/TicketCreationStatusPlugin TicketCreationStatusPlugin] and [http://trac-hacks.org/wiki/TicketConditionalCreationStatusPlugin TicketConditionalCreationStatusPlugin]'' |
| | 48 | |
| | 49 | * 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/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin] is close with set_owner_to_field, but we need something like set_field_to_owner. |
| | 50 | |
| | 51 | ''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.'' |
| | 52 | |
| | 53 | * I'd like to track the time a ticket is in each state, adding up 'disjoints' intervals in the same state. |
| | 54 | |
| | 55 | ''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.'' |
