Changes between Version 6 and Version 7 of TicketConditionalCreationStatusPlugin


Ignore:
Timestamp:
Jun 21, 2011 11:40:04 AM (3 years ago)
Author:
bof
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketConditionalCreationStatusPlugin

    v6 v7  
    2626names that you want to use as conditions. 
    2727 
    28 For any of the ''criteria'' you can then write variables '''<fieldname>.owned''' or '''<fieldname>.unowned''', 
    29 with values like '''<fieldcontent> -> <ticketstatus>'''. 
     28For any of the ''criteria'' you can then write variables '''<fieldname>.owned''' or '''<fieldname>.unowned'''. 
     29 * in the simplest form, such a variable takes the form {{{<fieldcontent> -> <ticketstatus>}}} 
     30 * you can also give several such rules, like {{{<content1> -> <status1>, <content2> -> <status2>}}} 
     31 * when you have several content values that should map to the same status, you can use {{{<content1>|<content2> -> <status>}}} 
    3032 
    3133== Example == 
    3234 
    33 The following example will make tickets of type '''task''' start out 
    34 as '''assigned''', instead of ''new'', if the owner is set at creation time: 
     35The following example will make ''owned'' tickets of types '''task''' and '''task-dev''' 
     36start out as '''assigned''', instead of ''new'', and tickets of type '''plan'' start 
     37out as '''new_plan'''. 
    3538 
    3639{{{ 
    3740[ticketconditionalcreationstatus] 
    3841criteria = type 
    39 type.owned = task -> assigned 
     42type.owned = task|task-dev -> assigned, plan -> new_plan 
    4043}}} 
    4144