Changes between Version 5 and Version 6 of AnalyzePlugin

Timestamp:

Dec 11, 2011, 1:39:59 AM (12 years ago)

Author:

Rob Guttman

Comment:

--

AnalyzePlugin

@@ -56 +56 @@
 == Example ==
 
-This plugin currently includes three analyses that can each be individually enabled for one or more reports.  Each analysis is configured by modifying the {{{[analyze]}}} section of {{{trac.ini}}} - see below for examples.  When an analysis is enabled for a report, an "Analyze..." button appears at the top of the report and the analysis' name will appear in the subsequent dialog box when the button is clicked.  You can either choose a single analysis or all analyses in this dialog box.  Selecting "All" will run them serially.
+This plugin currently includes three analyses that can each be individually enabled for one or more reports.  Each analysis is configured by modifying the {{{[analyze]}}} section of {{{trac.ini}}} - see below for examples.  When an analysis is enabled for a report, an '''Analyze...''' button appears at the top of the report and the analysis' name will appear in the subsequent dialog box when the button is clicked.  You can either choose a single analysis or all analyses in this dialog box.  Selecting "All" will run them serially.
 
 ==== Milestone Dependency Analysis ====
-The popular [wiki:MasterTicketsPlugin master tickets plugin] enables specifying dependencies amongst tickets and visualizes them via graphviz.  However, it does not provide tools to help manage these dependencies including detecting when they're not scheduled in the correct dependency order.  That's where this Milestone Dependency Analysis comes in.
+The popular [wiki:MasterTicketsPlugin master tickets plugin] enables specifying dependencies amongst tickets and visualizes them via graphviz.  However, it doesn't help manage these dependencies such as detecting when dependencies are scheduled out of order.  That's where this Milestone Dependency Analysis comes in.
 
 [[Image(issue-milestone.png)]]
 
-This analysis detects when a ticket in a given report has a dependency (a "blockedby" ticket) that is in a future milestone (or not scheduled in any milestone).  This works with either semantics for blockedby tickets:
+This analysis detects when a ticket in a given report has a dependency (a {{{blockedby}}} ticket) that is in a future milestone (or not scheduled in any milestone).  This works with either of the following semantics for {{{blockedby}}} tickets:
 
- * blockedby tickets are ''peer'' ordering relationships
- * blockedby tickets are ''project (aka parent-child) relationships)'' - where the parent/project's milestone is the latest milestone for the work to be completed
+ * {{{blockedby}}} tickets are ''peer'' ordering relationships
+ * {{{blockedby}}} tickets are ''project (aka parent-child) relationships)'' - where the parent/project's milestone is the latest milestone for the work to be completed
 
 To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows: