Changes between Version 8 and Version 9 of DynamicVariablesPlugin

Timestamp:

Dec 3, 2011, 4:23:57 AM (12 years ago)

Author:

Rob Guttman

Comment:

--

DynamicVariablesPlugin

@@ -36 +36 @@
     }}}
 
-    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.
+    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.
 
- 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.
+ 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.
 
 == Bugs/Feature Requests == 
@@ -57 +57 @@
 
 == Example ==
-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:
+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:
 {{{
 SELECT p.value AS __color__,
@@ -78 +78 @@
 [[Image(after.png)]]
 
-Completed milestones are skipped in the pulldown menu.
+Completed milestones are omitted from the pulldown menu.
 
 == Recent Changes ==