Changes between Version 28 and Version 29 of AnalyzePlugin


Ignore:
Timestamp:
Dec 12, 2011, 2:38:28 PM (3 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnalyzePlugin

    v28 v29  
    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.  You may also specify additional filters to skip tickets with certain field values:
     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 (pipe-delimited):
    9999{{{
    100100[analyze]
     
    102102}}}
    103103
    104 In 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.)
     104In this example, the {{{queue}}} field defines the queue in report 9 and will skip any ticket in this queue with {{{type}}} equal to "epic" or {{{phase}}} equal to "verifying" or "releasing".  (These would typically match the {{{WHERE}}} clause in the report's SQL.)
    105105
    106106Detected 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.