Changes between Version 3 and Version 4 of TracWorkflow

Timestamp:

Jun 22, 2007, 10:22:42 AM (17 years ago)

Author:

Christian Boos

Comment:

Upgrade content, taken from r5731, except for the Image source

TracWorkflow

@@ -5 +5 @@
 
 == The Default Ticket Workflow ==
-If you do not configure a custom workflow, the default workflow is described in [source:trunk/contrib/workflow/original-workflow.ini contrib/workflow/original-workflow.ini] '''FIXME'''.
+=== Environments upgraded from 0.10 ===
+When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section.
+The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10.
 
-[[Image(original-workflow.png)]]
+Graphically, that looks like this:
 
-You will probably want to look at the additional ticket workflows available, and [source:trunk/contrib/workflow/simple-workflow.ini contrib/workflow/simple-workflow.ini] in particular.
+[[Image(source:trunk/trac/htdocs/original-workflow.png)]]
+
+There are some significant "warts" in this; such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state.  Perfectly obvious, right?
+So you will probably want to migrate to "basic" workflow; `contrib/workflow/migrate_original_to_basic.py` may be helpful.
+
+=== Environments created with 0.11 ===
+When a new environment is created, a default workflow is configured in your trac.ini.  This workflow is the basic workflow (described in `basic-workflow.ini`), which is somewhat different from the workflow of the 0.10 releases.
+
+Graphically, it looks like this:
+
+[[Image(source:trunk/trac/htdocs/basic-workflow.png)]]
 
 == Additional Ticket Workflows ==
 
-There are several example workflows provided in the Trac source tree; look in [source:trunk/contrib/workflow contrib/workflow] for `.ini` config sections.  One of those may be a good match for what you want.
+There are several example workflows provided in the Trac source tree; look in `contrib/workflow` for `.ini` config sections.  One of those may be a good match for what you want.
 
 == Basic Ticket Workflow Customization ==
@@ -19 +31 @@
 Create a `[ticket-workflow]` section in `trac.ini`.
 Within this section, each entry is an action that may be taken on a ticket. 
-For example, consider the `accept` action from [source:trunk/contrib/workflow/simple-workflow.ini simple-workflow.ini]:
+For example, consider the `accept` action from `simple-workflow.ini`:
 {{{
 accept = new,accepted -> accepted
@@ -32 +44 @@
  - del_owner -- Clear the owner field.
  - set_owner -- Sets the owner to the selected or entered owner.
+   - ''actionname''`.set_owner` may optionally be set to a comma delimited list or a single value.
  - set_owner_to_self -- Sets the owner to the logged in user.
  - del_resolution -- Clears the resolution field
  - set_resolution -- Sets the resolution to the selected value.
+   - ''actionname''`.set_resolution` may optionally be set to a comma delimited list or a single value.
  - leave_status -- Displays "leave as <current status>" and makes no change to the ticket.
 '''Note:''' Specifying conflicting operations (such as `set_owner` and `del_owner`) has unspecified results.
@@ -58 +72 @@
 There are a couple of hard-coded constraints to the workflow.  In particular, tickets are created with status `new`, and tickets are expected to have a `closed` state.  Further, the default reports/queries treat any state other than `closed` as an open state.
 
-While creating or modifying a ticket workfow, [source:trunk/contrib/workflow/workflow_parser.py contrib/workflow/workflow_parser.py] may be useful.  It can create `.dot` files that [http://www.graphviz.org/ Graphviz] understands to provide a visual description of the workflow.
+While creating or modifying a ticket workfow, `contrib/workflow/workflow_parser.py` may be useful.  It can create `.dot` files that GraphViz understands to provide a visual description of the workflow.
 
 == Advanced Ticket Workflow Customization ==
 
-If the customization above is not extensive enough for your needs, you can extend the workflow using plugins.  These plugins can provide additional operations for the workflow (like code_review), or implement side-effects for an action (such as triggering a build).  Look at [source:trunk/sample-plugins/workflow sample-plugins/workflow] for a few simple examples to get started.
+If the customization above is not extensive enough for your needs, you can extend the workflow using plugins.  These plugins can provide additional operations for the workflow (like code_review), or implement side-effects for an action (such as triggering a build).  Look at `sample-plugins/workflow` for a few simple examples to get started.
 
-But if even that is not enough, you can disable !DefaultTicketActionController, and create a plugin that completely replaces it.
+But if even that is not enough, you can disable DefaultTicketActionController, and create a plugin that completely replaces it.