Changes between Version 15 and Version 16 of DynamicVariablesPlugin

Timestamp:

Oct 16, 2016, 7:02:37 AM (8 years ago)

Author:

figaro

Comment:

Moved example to functional description

DynamicVariablesPlugin

@@ -11 +11 @@
 
 !JavaScript is required for the latter feature.
+
+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:
+{{{#!sql
+SELECT p.value AS __color__, t.id AS ticket, summary, component, severity, reporter
+FROM ticket t
+  LEFT OUTER JOIN milestone m ON t.milestone = m.name
+  LEFT JOIN enum p ON p.name = t.severity AND p.type = 'severity'
+  LEFT OUTER JOIN ticket_custom q ON q.ticket = t.id AND q.name = 'queue'
+WHERE q.value = '$QUEUE'
+  AND milestone = '$MILESTONE'
+ORDER BY m.due ASC, p.value
+}}}
+
+The result is as follows:
+
+=== Before
+
+[[Image(before.png)]]
+
+=== After
+
+[[Image(after.png)]]
+
+Completed milestones are omitted from the dropdown menu.
 
 == Bugs/Feature Requests
@@ -59 +83 @@
  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.
 
-== Example
-
-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:
-{{{#!sql
-SELECT p.value AS __color__, t.id AS ticket, summary, component, severity, reporter
-FROM ticket t
-  LEFT OUTER JOIN milestone m ON t.milestone = m.name
-  LEFT JOIN enum p ON p.name = t.severity AND p.type = 'severity'
-  LEFT OUTER JOIN ticket_custom q ON q.ticket = t.id AND q.name = 'queue'
-WHERE q.value = '$QUEUE'
-  AND milestone = '$MILESTONE'
-ORDER BY m.due ASC, p.value
-}}}
-
-The result is as follows:
-
-=== Before
-
-[[Image(before.png)]]
-
-=== After
-
-[[Image(after.png)]]
-
-Completed milestones are omitted from the dropdown menu.
-
 == Recent Changes