Changes between Version 29 and Version 30 of AnalyzePlugin
- Timestamp:
- Dec 12, 2011, 1:45:02 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnalyzePlugin
v29 v30 102 102 }}} 103 103 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.)104 In this example, the {{{queue}}} field defines the queue in report 9 and the analysis 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. … … 116 116 project_reports = 19 117 117 project_type = epic 118 queue_fields.19 = queue,milestone,type!=epic,phase!=verifying|releasing 118 119 }}} 119 120 120 The {{{project_type}}} option above is the name that you call your projects (e.g., "epic" (the default), "project", etc.). These tickets do not have to be of any specific ticket type - at least not at this time. 121 The {{{project_type}}} option above is the name that you call your projects (e.g., "epic" (the default), "project", etc.). These tickets do not have to be of any specific ticket type - at least not at this time. This analysis uses the same queue fields configuration as the Queue Dependency Analysis above. 121 122 122 123 Detected problems are shown with an option to automatically fix the problem by moving the sub-task/child tickets above or below each other in their queue (to match their parent's relative positions) - see screenshot above.