Changes between Version 69 and Version 70 of WorkFlow

Timestamp:

Jun 15, 2007, 5:22:25 PM (17 years ago)

Author:

Christian Boos

Comment:

document r5442, s/DefaultTicketActionController/ConfigurableTicketWorkflow/

WorkFlow

@@ -9 +9 @@
 
 === Phase 2 and beyond ===
-Phase 2 and beyond will bring in more of the functionality developed on the original workflow branch, such as custom ticket fields and field types provided by plugins.
+Phase 2 and beyond will bring in more of the functionality developed on the original workflow branch, such as custom ticket fields and field types provided by plugins (see also FieldRefactoring).
 
 See source:sandbox/workflow@3378 for the original incarnation of the WorkFlow branch, based on 0.10dev (last sync with trunk was with r3377, i.e. June 2006).
@@ -16 +16 @@
 ''implemented in phase1''
 
-Configurable workflow allows you to change the ticket states and state transitions.  A common desire is to have a "testing" state where QA can get involved.  The default WorkFlow implementation ([source:trunk/trac/ticket/api.py@5379#L148 DefaultTicketActionController]) allows you to configure that workflow from the trac.ini.
+Configurable workflow allows you to change the ticket states and state transitions.  A common desire is to have a "testing" state where QA can get involved.  The default WorkFlow implementation ([source:trunk/trac/ticket/default_workflow.py@5693#L111 ConfigurableTicketWorkflow]) allows you to configure that workflow from the trac.ini.
 
 There are several working [source:trunk/contrib/workflow configuration examples] available.  (Along with a couple tools for working with workflow configurations.)  There are also some pretty diagrams on WorkFlow/Examples.
 
 But you can do more than that with plugins.  Plugins may augment the default WorkFlow, adding actions and side-effects to ticket state transitions.   There are a few working [source:trunk/sample-plugins/workflow plugin examples] available.  (They're simplistic, but should be useful nonetheless.)  Plugins may also add actions that do not affect ticket state.
-If a drastically different WorkFlow is needed, !DefaultTicketActionController may be disabled and entirely replaced by a plugin.
+If a drastically different WorkFlow is needed, !ConfigurableTicketWorkflow may be disabled and entirely replaced by a plugin.
 
 == Plugin Configurable Ticket Fields ==