Changes between Version 20 and Version 21 of AdvancedTicketWorkflowPlugin

Timestamp:

Feb 22, 2010, 1:42:11 AM (14 years ago)

Author:

Eli Carter

Comment:

add further clarification of the triage operation

AdvancedTicketWorkflowPlugin

@@ -95 +95 @@
 <someaction>.triage_split = defect->new_defect,task->new_task,enhancement->new_enhancement
 }}}
+
+    The most common request is to use a different workflow based on the ticket type.  Let's simplify that case slightly for the sake of this example and assume that there are only two ticket types, `defect` and `enhancement`.  We'll say that `defect`s require a `qa` step, but `enhancement`s do not.
+{{{
+accept = new -> *
+accept.name = Accept ticket into workflow
+accept.operations = triage
+accept.triage_field = type
+accept.triage_split = defect->new_defect,enhancement->new_enhancement
+
+resolve_enh = new_enhancement -> closed
+resolve_enh.name = resolve
+resolve_enh.operations = set_resolution
+
+submittotest = new_defect -> qa
+submittotest.name = Submit to Test
+
+resolve_def = qa -> closed
+resolve_def.name = resolve
+resolve_def.operations = set_resolution
+}}}
+
  * xref (TicketWorkflowOpXRef)
     Adds a comment to the ticket specified in the text field.  Enter either the bare ticket number or '#' + ticket number.  The format of the comment to be added to the other ticket is given as a python string with a single `%s` in it.  That format string defaults to `'Ticket %s is related to this ticket'`.