Changes between Version 30 and Version 31 of AnalyzePlugin


Ignore:
Timestamp:
Dec 15, 2011 4:37:42 PM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnalyzePlugin

    v30 v31  
    116116project_reports = 19 
    117117project_type = epic 
     118refresh_report = 9 
    118119queue_fields.19 = queue,milestone,type!=epic,phase!=verifying|releasing 
    119120}}} 
    120121 
    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. 
     122The {{{project_type}}} option above is the ticket type of your projects (e.g., "epic" (the default), "project", etc.).  Project tickets must be of this type. 
     123 
     124The default behavior of an analysis is to refresh the current report if any fixes were made.  This is so that changes can be viewed (assuming they would change the content of the report).  In the case of Project Dependency Analysis, you would usually also need another report refreshed - i.e., the impacted work queue.  Use the {{{refresh_report}}} option to specify this impacted work queue which will also get refreshed at the end of this analysis if there were any fixes.  You can add params to the report as well if needed: 
     125{{{ 
     126[analyze] 
     127refresh_report = 9?max=1000 
     128}}} 
     129 
     130This analysis uses the same queue fields configuration as the Queue Dependency Analysis above. 
    122131 
    123132Detected 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.