Changes between Version 20 and Version 21 of AdvancedTicketWorkflowPlugin


Ignore:
Timestamp:
Feb 22, 2010 2:42:11 AM (5 years ago)
Author:
retracile
Comment:

add further clarification of the triage operation

Legend:

Unmodified
Added
Removed
Modified
  • AdvancedTicketWorkflowPlugin

    v20 v21  
    9595<someaction>.triage_split = defect->new_defect,task->new_task,enhancement->new_enhancement 
    9696}}} 
     97 
     98    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. 
     99{{{ 
     100accept = new -> * 
     101accept.name = Accept ticket into workflow 
     102accept.operations = triage 
     103accept.triage_field = type 
     104accept.triage_split = defect->new_defect,enhancement->new_enhancement 
     105 
     106resolve_enh = new_enhancement -> closed 
     107resolve_enh.name = resolve 
     108resolve_enh.operations = set_resolution 
     109 
     110submittotest = new_defect -> qa 
     111submittotest.name = Submit to Test 
     112 
     113resolve_def = qa -> closed 
     114resolve_def.name = resolve 
     115resolve_def.operations = set_resolution 
     116}}} 
     117 
    97118 * xref (TicketWorkflowOpXRef) 
    98119    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'`.