Changes between Version 28 and Version 29 of AnalyzePlugin
- Timestamp:
- Dec 12, 2011, 1:38:28 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnalyzePlugin
v28 v29 96 96 }}} 97 97 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 :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 (pipe-delimited): 99 99 {{{ 100 100 [analyze] … … 102 102 }}} 103 103 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.)104 In 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.) 105 105 106 106 Detected 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.