Changes between Version 6 and Version 7 of TicketConditionalCreationStatusPlugin
- Timestamp:
- Jun 21, 2011, 9:40:04 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TicketConditionalCreationStatusPlugin
v6 v7 26 26 names that you want to use as conditions. 27 27 28 For any of the ''criteria'' you can then write variables '''<fieldname>.owned''' or '''<fieldname>.unowned''', 29 with values like '''<fieldcontent> -> <ticketstatus>'''. 28 For 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>}}} 30 32 31 33 == Example == 32 34 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: 35 The following example will make ''owned'' tickets of types '''task''' and '''task-dev''' 36 start out as '''assigned''', instead of ''new'', and tickets of type '''plan'' start 37 out as '''new_plan'''. 35 38 36 39 {{{ 37 40 [ticketconditionalcreationstatus] 38 41 criteria = type 39 type.owned = task -> assigned42 type.owned = task|task-dev -> assigned, plan -> new_plan 40 43 }}} 41 44