Changes between Version 5 and Version 6 of AnalyzePlugin
- Timestamp:
- Dec 11, 2011, 1:39:59 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnalyzePlugin
v5 v6 56 56 == Example == 57 57 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.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. 59 59 60 60 ==== 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 dependencyorder. That's where this Milestone Dependency Analysis comes in.61 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. 62 62 63 63 [[Image(issue-milestone.png)]] 64 64 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 blockedbytickets: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 of the following semantics for {{{blockedby}}} tickets: 66 66 67 * blockedbytickets are ''peer'' ordering relationships68 * blockedbytickets are ''project (aka parent-child) relationships)'' - where the parent/project's milestone is the latest milestone for the work to be completed67 * {{{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 69 69 70 70 To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows: