Changes between Version 4 and Version 5 of TracIdeas/TracWorkflow

Timestamp:

Jan 15, 2015, 10:45:33 AM (9 years ago)

Author:

Ryan J Ollos

Comment:

Page cleanup.

TracIdeas/TracWorkflow

@@ -22 +22 @@
 == Workflow Actions
 
-//(this content was copied from the TracWorkflow page and should be cleaned up)//
-
 If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket.
 
- * the "operation" could be on the nodes, possible operations are:
-   * '''preops''': automatic, before entering the state/activity
-   * '''postops''': automatic, when leaving the state/activity
-   * '''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.
-''This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement.''
+* the "operation" could be on the nodes, possible operations are:
+ * '''preops''': automatic, before entering the state/activity
+ * '''postops''': automatic, when leaving the state/activity
+ * '''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.
+ 
+ ''This appears to add complexity without adding functionality; please provide a detailed example where these additions allow something currently impossible to implement.''
 
- * operations could be anything: sum up the time used for the activity, or just write some statistical fields like 
-''A workflow plugin can add an arbitrary workflow operation, so this is already possible.''
+* operations could be anything: sum up the time used for the activity, or just write some statistical fields like 
 
- * set_actor should be an operation allowing to set the owner, e.g. as a "preop":
+ ''A workflow plugin can add an arbitrary workflow operation, so this is already possible.''
+
+* set_actor should be an operation allowing to set the owner, e.g. as a "preop":
    * either to a role, a person
    * entered fix at define time, or at run time, e.g. out of a field, or select.
-''This is either duplicating the existing `set_owner` operation, or needs to be clarified.''
+ 
+ ''This is either duplicating the existing `set_owner` operation, or needs to be clarified.''
 
  * Actions should be selectable based on the ticket type (different Workflows for different tickets)
-''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s `triage` operation.''
+ 
+ ''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s `triage` operation.''
 
- * 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.
+* 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.
 
-''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.''
+ ''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.''
 
- * I'd like to track the time a ticket is in each state, adding up 'disjoints' intervals in the same state.
+* I'd like to track the time a ticket is in each state, adding up 'disjoints' intervals in the same state.
 
-''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.''
+ ''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.''
 
 
 == Workflow attributes
 
- * `restrict_owner` field for `set_owner` and `may_set_owner` operations that overrides the global `[ticket] restrict_owner` setting.
+ * `restrict_owner` field for `set_owner` and `may_set_owner` operations that overrides, or replaces, the global `[ticket] restrict_owner` setting.
 
 ----