Changes between Version 17 and Version 18 of MultipleWorkflowPlugin

Timestamp:

May 2, 2015, 10:24:05 AM (9 years ago)

Author:

Cinc-th

Comment:

Enhanced the description.

MultipleWorkflowPlugin

@@ -4 +4 @@
 == Description
 
-The MultipleWorkflowPlugin replaces the !ConfigurableTicketPlugin used by trac to control what actions a ticket can do reading `[ticket-workflow]` session.
+The MultipleWorkflowPlugin replaces the !ConfigurableTicketPlugin used by Trac to control what actions a ticket can do reading `[ticket-workflow]` section.
 
-With MultipleWorkflowPlugin trac can read the workflow based on the type of ticket that is considering. If a section for that ticket type doesn't exist than it uses the default workflow.
+With MultipleWorkflowPlugin Trac can read the workflow based on the type of ticket. If a section for that ticket type doesn't exist than it uses the default workflow, see [#Example Example].
+
+The plugin works with Trac 0.11 and 0.12 and maybe with Trac 1.x (not tested).
+
+See also TypedTicketWorkflowPlugin.
+=== What's the Difference to TypedTicketWorkflowPlugin? ===
+With MultipleWorkflowPlugin you may have an exclusive workflow section for each ticket type like this:
+{{{#!ini
+[ticket-workflow]
+# Default workflow
+approve = new, reopened -> approved
+approve.operations = del_resolution
+ ...
+
+[ticket-workflow-Foo]
+# Workflow for ticket type 'Foo'
+do_foo = new -> foo
+ ...
+
+[ticket-workflow-Bar]
+# Workflow for ticket type 'Bar'
+do_bar = new -> bar
+ ...
+}}}
+
+With TypedTicketWorkflowPlugin you specify restrictions for ticket types in the default workflow by adding them to the transitions like:
+{{{#!ini
+[ticket-workflow]
+approve = new, reopened -> approved
+approve.operations = del_resolution
+# approve is only valid for ticket types 'defect' and 'feature'
+approve.ticket_type = defect, feature
+ ...
+}}}
+
+The former is easier to manage if you have several ticket types with vastly different workflows.
+
 
 == Bugs/Feature Requests