Changes between Version 8 and Version 9 of DynamicVariablesPlugin


Ignore:
Timestamp:
Dec 3, 2011 5:23:57 AM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DynamicVariablesPlugin

    v8 v9  
    3636    }}} 
    3737 
    38     In the above example, {{{daysback}}} is not a custom ticket field but can be set a {{{DAYSBACK}}} dynamic variable by a pulldown with the specified options.  A {{{[dynvars]}}} section is not needed for dynamic variables that exactly match built-in or custom field names as shown in the screenshots below. 
     38    In the above example, {{{daysback}}} is not a custom ticket field but can set a {{{DAYSBACK}}} dynamic variable via a pulldown with the specified options.  A {{{[dynvars]}}} section is not needed to configure dynamic variables that exactly match built-in or custom field names as shown in the screenshots below. 
    3939 
    40  4. Create/modify reports so that the name used for dynamic variables exactly match the name of the select field that it corresponds to.  See an example below. 
     40 4. Create/modify reports so that the names used for dynamic variables exactly match the names of the select field that it corresponds to.  See an example below. 
    4141 
    4242== Bugs/Feature Requests ==  
     
    5757 
    5858== Example == 
    59 The only configuration options are in defining SQL reports.  For example, a report for a specific {{{milestone}}} that also queries for a custom {{{queue}}} select field could be defined like this: 
     59The only required configuration is in defining SQL reports.  For example, a report for a specific {{{milestone}}} that also queries for a custom {{{queue}}} select field could be defined like this: 
    6060{{{ 
    6161SELECT p.value AS __color__, 
     
    7878[[Image(after.png)]] 
    7979 
    80 Completed milestones are skipped in the pulldown menu. 
     80Completed milestones are omitted from the pulldown menu. 
    8181 
    8282== Recent Changes ==