Changes between Version 6 and Version 7 of AnalyzePlugin
- Timestamp:
- Dec 11, 2011, 1:41:43 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnalyzePlugin
v6 v7 74 74 }}} 75 75 76 Detected problems are shown with an option to automatically fix the problem by moving tickets into appropriate milestones .76 Detected problems are shown with an option to automatically fix the problem by moving tickets into appropriate milestones - see screenshot above. 77 77 78 78 ==== Queue Dependency Analysis ==== … … 96 96 In this example, report 2 uses both {{{queue}}} and {{{milestone}}} fields to define a queue whereas report 9 uses only the {{{queue}}} field. 97 97 98 Detected problems are shown with an option to automatically fix the problem by moving tickets above or below each other in the queue .98 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. 99 99 100 100 ==== Project Dependency Analysis ==== … … 112 112 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. 113 113 114 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 the queue (to map their parent's relative positions) .114 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 the queue (to map their parent's relative positions) - see screenshot above. 115 115 116 116 == Tips! ==
