Changes between Version 30 and Version 31 of DynamicFieldsPlugin


Ignore:
Timestamp:
Dec 21, 2011 7:17:17 PM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DynamicFieldsPlugin

    v30 v31  
    109109[ticket-custom] 
    110110captain.copy_from = owner 
    111 captain.overwrite = false 
    112 }}} 
    113  
    114 The default copy behavior is to not overwrite a value if one already exists.  To always copy the value, set the {{{overwrite}}} option to ''true''. 
     111}}} 
     112 
     113The default copy behavior is to not overwrite a value if one already exists.  To always copy the value, add {{{(overwrite)}}} as follows: 
     114{{{ 
     115[ticket-custom] 
     116captain.copy_from = (overwrite) owner 
     117}}} 
    115118 
    116119 
     
    149152{{{ 
    150153[ticket-custom] 
    151 milestone.set_when_phase = implementation|verifying|releasing 
    152 milestone.set_to = milestone3 
    153 milestone.overwrite = false 
    154 }}} 
    155  
    156 When the {{{phase}}} field changes to either ''implementation'', ''verifying'', or ''releasing'', then the {{{milestone}}} will get set to ''milestone3''.  To avoid needing to update the current milestone's value, you can alternatively use the special ''"!"'' value which specifies to set the field to the first non-empty value: 
    157 {{{ 
    158 milestone.set_to = ! 
    159 }}} 
    160  
    161 If you want to enable each user to set the value as a preference, you should omit the {{{set_to}}} option entirely and instead specify the rule as follows: 
    162 {{{ 
    163 milestone.set_when_phase = implementation|verifying|releasing (pref) 
    164 milestone.overwrite = false 
    165 }}} 
    166  
    167 Learn more about user preferences below.  The default set behavior is to not overwrite a value if one already exists.  To always set the value, set the {{{overwrite}}} option to ''true''. 
     154milestone.set_to_milestone3_when_phase = implementation|verifying|releasing 
     155}}} 
     156 
     157When the {{{phase}}} field changes to either ''implementation'', ''verifying'', or ''releasing'', then the {{{milestone}}} will get set to ''milestone3''.  To avoid needing to update the current milestone's value in the rule, you can alternatively use the special ''"!"'' value which specifies to set the field to the first non-empty value: 
     158{{{ 
     159milestone.set_to_!_when_phase = implementation|verifying|releasing 
     160}}} 
     161 
     162If you want to enable each user to set the value as a preference, you set to an asterisk {{{*}}} as follows: 
     163{{{ 
     164milestone.set_to_*_when_phase = implementation|verifying|releasing (pref) 
     165}}} 
     166 
     167Learn more about user preferences below.  The default set behavior is to not overwrite a value if one already exists.  To always set the value, add {{{(overwrite)}}} as follows: 
     168{{{ 
     169[ticket-custom] 
     170milestone.set_to_!_when_phase = (overwrite) implementation|verifying|releasing (pref) 
     171}}} 
    168172 
    169173