| 34 | | parent-child |
| 35 | | peer |
| | 56 | 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. |
| | 57 | |
| | 58 | ==== Milestone Dependency Analysis ==== |
| | 59 | 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. |
| | 60 | |
| | 61 | 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). To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows: |
| | 62 | {{{ |
| | 63 | [analyze] |
| | 64 | milestone_reports = 1,9 |
| | 65 | }}} |
| | 66 | |
| | 67 | Detected problems are shown with an option to automatically fix the problem by moving tickets into appropriate milestones. |
| | 68 | |
| | 69 | ==== Queue Dependency Analysis ==== |
| | 70 | The [wiki:QueuesPlugin queues plugin] converts one or more reports into work queues. These queues enable you to drag and drop tickets above and below one another signifying their relative priority. Each ticket's relative position is maintained in custom field usually named {{{position}}} (but can be named anything). Dependencies amongst tickets in a queue have similar problems as tickets across milestones - in this case, a dependent ticket should precede (i.e., appear higher in the queue which means have a lower {{{position}}} value), but it can be difficult to manuually catch all of these dependency violations. That's where this Queue Dependency Analysis comes in. |
| | 71 | |
| | 72 | This analysis detects when a ticket in a given report has a dependency (a "blockedby" ticket) whose {{{position}}} comes after this ticket's (or has no {{{position}}} yet at all). To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows: |
| | 73 | {{{ |
| | 74 | [analyze] |
| | 75 | queue_reports = 2,9 |
| | 76 | queue_fields = queue,milestone |
| | 77 | }}} |
| | 78 | |
| | 79 | The {{{queue_fields}}} option above tells this analysis what fields define a queue. Queues can be defined by one or more fields such as the {{{milestone}}} field, a custom {{{queue}}} field, both or other fields. If you have different reports using different definitions, you can define report-specific queue field definitions as follows: |
| | 80 | {{{ |
| | 81 | [analyze] |
| | 82 | queue_fields.9 = queue |
| | 83 | }}} |
| | 84 | |
| | 85 | In this example, report 2 uses both {{{queue}}} and {{{milestone}}} fields to define a queue whereas report 9 uses only the {{{queue}}} field. |
| | 86 | |
| | 87 | Detected problems are shown with an option to automatically fix the problem by moving tickets above or below each other in the queue. |
| | 88 | |
| | 89 | == Tips! == |
| | 90 | * If this tool's project management changes generates emails that are of little value to your team, then you can quiet them by enabling "Quiet Mode" using the [wiki:QuietPlugin Quiet Plugin]. |
