Changes between Version 4 and Version 5 of TracWorkflow

Ignore:
Timestamp:
Apr 18, 2013 10:02:31 AM (9 years ago)
Comment:

--

Unmodified
Added
Removed
Modified
• TracWorkflow

 v4 Graphically, that looks like this: [[Image(htdocs:../common/guide/original-workflow.png)]] {{{#!Workflow width=500 height=240 leave = * -> * leave.operations = leave_status leave.default = 1 accept = new -> assigned accept.permissions = TICKET_MODIFY accept.operations = set_owner_to_self resolve = new,assigned,reopened -> closed resolve.permissions = TICKET_MODIFY resolve.operations = set_resolution reassign = new,assigned,reopened -> new reassign.permissions = TICKET_MODIFY reassign.operations = set_owner reopen = closed -> reopened reopen.permissions = TICKET_CREATE reopen.operations = del_resolution }}} 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? Graphically, it looks like this: [[Image(htdocs:../common/guide/basic-workflow.png)]] {{{#!Workflow width=700 height=300 leave = * -> * leave.operations = leave_status leave.default = 1 accept = new,assigned,accepted,reopened -> accepted accept.permissions = TICKET_MODIFY accept.operations = set_owner_to_self resolve = new,assigned,accepted,reopened -> closed resolve.permissions = TICKET_MODIFY resolve.operations = set_resolution reassign = new,assigned,accepted,reopened -> assigned reassign.permissions = TICKET_MODIFY reassign.operations = set_owner reopen = closed -> reopened reopen.permissions = TICKET_CREATE reopen.operations = del_resolution }}} == Additional Ticket Workflows == - 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. {{{ Example: - ''actionname''.set_resolution may optionally be set to a comma delimited list or a single value. Example: {{{ resolve_new = new -> closed resolve_new.name = resolve resolve_new.permissions = TICKET_MODIFY resolve_new.set_resolution = invalid,wontfix }}} }}} - leave_status -- Displays "leave as " and makes no change to the ticket. '''Note:''' Specifying conflicting operations (such as set_owner and del_owner) has unspecified results. 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, 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 workflow, 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. This can be done as follows (your install path may be different). === How to combine the tracopt.ticket.commit_updater with the testing workflow === The [[source:trunk/tracopt/ticket/commit_updater.py|tracopt.ticket.commit_updater]] is the optional component that [[TracRepositoryAdmin#trac-post-commit-hook|replaces the old trac-post-commit-hook]], in Trac 0.12. The [[trac:source:trunk/tracopt/ticket/commit_updater.py|tracopt.ticket.commit_updater]] is the optional component that [[TracRepositoryAdmin#trac-post-commit-hook|replaces the old trac-post-commit-hook]], in Trac 0.12. By default it reacts on some keywords found in changeset message logs like ''close'', ''fix'' etc. and performs the corresponding workflow action. If you have a more complex workflow, like the testing stage described above and you want the ''closes'' keyword to move the ticket to the ''testing'' status instead of the ''closed'' status, you need to adapt the code a bit. Have a look at the [[0.11/TracWorkflow#How-ToCombineSVNtrac-post-commit-hookWithTestWorkflow|Trac 0.11 recipe]] for the trac-post-commit-hook, this will give you some ideas about how to modify the component. Have a look at the [[trac:wiki:0.11/TracWorkflow#How-ToCombineSVNtrac-post-commit-hookWithTestWorkflow|Trac 0.11 recipe]] for the trac-post-commit-hook, this will give you some ideas about how to modify the component. == Example: Add simple optional generic review state == leave.default = 1 leave.operations = leave_status reassign = new,assigned,reopened -> new reassign = new,assigned,accepted,reopened -> assigned reassign.operations = set_owner reassign.permissions = TICKET_MODIFY == some ideas for next steps == New enhancement ideas for the workflow system should be filed as enhancement tickets against the ticket system component.  If desired, add a single-line link to that ticket here.  Also look at the [th:wiki:AdvancedTicketWorkflowPlugin] as it provides experimental operations. New enhancement ideas for the workflow system should be filed as enhancement tickets against the ticket system component.  If desired, add a single-line link to that ticket here.  Also look at the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin] as it provides experimental operations. If you have a response to the comments below, create an enhancement ticket, and replace the description below with a link to the ticket. * Actions should be selectable based on the ticket type (different Workflows for different tickets) ''Look into the [th:wiki:AdvancedTicketWorkflowPlugin]'s triage operation.'' ''Look into the [http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin AdvancedTicketWorkflowPlugin]'s triage operation.'' * I'd wish to have an option to perform automatic status changes. In my case, I do not want to start with "new", but with "assigned". So tickets in state "new" should automatically go into state "assigned". Or is there already a way to do this and I just missed it? ''Have a look at [http://trac-hacks.org/wiki/TicketCreationStatusPlugin TicketCreationStatusPlugin] and [http://trac-hacks.org/wiki/TicketConditionalCreationStatusPlugin TicketConditionalCreationStatusPlugin]'' * 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'd like to track the time a ticket is in each state, adding up 'disjoints' intervals in the same state.