Changes between Version 5 and Version 6 of AnalyzePlugin


Ignore:
Timestamp:
Dec 11, 2011 2:39:59 AM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnalyzePlugin

    v5 v6  
    5656== Example ==
    5757
    58 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.
     58This 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.
    5959
    6060==== Milestone Dependency Analysis ====
    61 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.
     61The 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.
    6262
    6363[[Image(issue-milestone.png)]]
    6464
    65 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:
     65This 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:
    6666
    67  * blockedby tickets are ''peer'' ordering relationships
    68  * blockedby tickets are ''project (aka parent-child) relationships)'' - where the parent/project's milestone is the latest milestone for the work to be completed
     67 * {{{blockedby}}} tickets are ''peer'' ordering relationships
     68 * {{{blockedby}}} tickets are ''project (aka parent-child) relationships)'' - where the parent/project's milestone is the latest milestone for the work to be completed
    6969
    7070To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows: