Changes between Version 5 and Version 6 of DynamicVariablesPlugin


Ignore:
Timestamp:
Jan 2, 2011, 6:00:36 AM (6 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DynamicVariablesPlugin

    v5 v6  
    1515 1. Install the plugin (after downloading and unzipping):
    1616    {{{
    17     cd dynamicvariablesplugin/0.11
     17    cd dynamicvariablesplugin/0.12
    1818    sudo python setup.py bdist_egg
    1919    sudo cp dist/TracDynamicVariables*.egg /your/trac/location/plugins/
     
    3030    You can alternatively use the Trac Web Admin GUI to enable any or all rules.
    3131
    32  3. Create/modify reports so that the name used for dynamic variables exactly match the name of the select field that it corresponds to.  For example, a report for a specific {{{milestone}}} that also queries for a custom {{{queue}}} select field could be specified like this:
    33 {{{
    34 SELECT p.value AS __color__,
    35    t.id AS ticket, summary, component, severity, reporter,
    36    t.time AS created,
    37    changetime AS _changetime, t.description AS _description
    38   FROM ticket t
    39   LEFT OUTER JOIN milestone m ON t.milestone=m.name
    40   LEFT JOIN enum p ON p.name = t.severity AND p.type = 'severity'
    41   LEFT OUTER JOIN ticket_custom q ON q.ticket = t.id and q.name = 'queue'
    42   WHERE t.status <> 'closed' AND q.value = '$QUEUE'
    43     AND milestone= '$MILESTONE'
    44   ORDER BY m.due ASC, p.value, severity, t.time
    45 }}}
     32 3. 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.
    4633
    4734== Bugs/Feature Requests ==
     
    6249
    6350== Example ==
    64 There is (currently) no configuration options.  Here's what the changes look like once enabled:
     51The only configuration options are in specifying reports as per 3 above.  For example, a report for a specific {{{milestone}}} that also queries for a custom {{{queue}}} select field could be specified like this:
     52{{{
     53SELECT p.value AS __color__,
     54   t.id AS ticket, summary, component, severity, reporter
     55  FROM ticket t
     56  LEFT OUTER JOIN milestone m ON t.milestone = m.name
     57  LEFT JOIN enum p ON p.name = t.severity AND p.type = 'severity'
     58  LEFT OUTER JOIN ticket_custom q ON q.ticket = t.id and q.name = 'queue'
     59  WHERE q.value = '$QUEUE'
     60    AND milestone = '$MILESTONE'
     61  ORDER BY m.due ASC, p.value
     62}}}
     63
     64Here's what this report would look like both before and after this plugin is installed and enabled:
    6565
    6666=== Before ===