Changes between Version 6 and Version 7 of TracWorkflow

Timestamp:

Jul 24, 2007, 7:10:54 AM (17 years ago)

Author:

shepting@…

Comment:

Added clarifications for making your custom workflow.

TracWorkflow

@@ -25 +25 @@
 == Additional Ticket Workflows ==
 
-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.
+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. They can be pasted into the `[ticket-workflow]` section of your `trac.ini` file.
 
 == Basic Ticket Workflow Customization ==
@@ -79 +79 @@
 sudo ./showworkflow /srv/trac/PlannerSuite/conf/trac.ini
 }}}
-And then open up the resulting trac.pdf file created by the script.
+And then open up the resulting `trac.pdf` file created by the script (it will be in the same directory as the `trac.ini` file).
 
 After you have changed a workflow, you need to restart apache for the changes to take effect. This is important, because the changes will still show up when you run your script, but all the old workflow steps will still be there until the server is restarted.
@@ -85 +85 @@
 == 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 `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) that may not be merely simple state changes.  Look at `sample-plugins/workflow` for a few simple examples to get started.
 
 But if even that is not enough, you can disable the !ConfigurableTicketWorkflow component and create a plugin that completely replaces it.