Changes between Version 8 and Version 9 of DynamicVariablesPlugin
- Timestamp:
- Dec 3, 2011, 4:23:57 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DynamicVariablesPlugin
v8 v9 36 36 }}} 37 37 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 fordynamic 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. 39 39 40 4. Create/modify reports so that the name used for dynamic variables exactly match the nameof 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. 41 41 42 42 == Bugs/Feature Requests == … … 57 57 58 58 == Example == 59 The only configuration options arein 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:59 The 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: 60 60 {{{ 61 61 SELECT p.value AS __color__, … … 78 78 [[Image(after.png)]] 79 79 80 Completed milestones are skipped inthe pulldown menu.80 Completed milestones are omitted from the pulldown menu. 81 81 82 82 == Recent Changes ==