Changes between Version 29 and Version 30 of AnalyzePlugin


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

--

Legend:

Unmodified
Added
Removed
Modified
  • AnalyzePlugin

    v29 v30  
    102102}}}
    103103
    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.)
     104In 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.)
    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.
     
    116116project_reports = 19
    117117project_type = epic
     118queue_fields.19 = queue,milestone,type!=epic,phase!=verifying|releasing
    118119}}}
    119120
    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.
     121The {{{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.
    121122
    122123Detected 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.