Changes between Version 27 and Version 28 of AnalyzePlugin


Ignore:
Timestamp:
Dec 12, 2011, 2:15:02 PM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnalyzePlugin

    v27 v28  
    9696}}}
    9797
    98 In this example, report 2 uses both {{{queue}}} and {{{milestone}}} fields to define a queue whereas report 9 uses only the {{{queue}}} field.
     98In this example, report 2 uses both {{{queue}}} and {{{milestone}}} fields to define a queue whereas report 9 uses only the {{{queue}}} field.  You may also specify additional filters to skip tickets with certain field values:
     99{{{
     100[analyze]
     101queue_fields.9 = queue,type!=epic,phase!=verifying|releasing
     102}}}
     103
     104In this example, the {{{queue}}} field defines the queue in report 2 and any ticket in this queue with {{{type}}} equal to "epic" or {{{phase}}} equal to "verifying" or "releasing" will be skipped.  (These would typically match the {{{WHERE}}} clause in the report's SQL.)
    99105
    100106Detected problems are shown with an option to automatically fix the problem by moving tickets above or below each other in the queue - see screenshot above.