Changes between Version 35 and Version 36 of AnalyzePlugin
- Timestamp:
- Apr 9, 2012, 1:56:58 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnalyzePlugin
v35 v36 138 138 [[Image(rollup-project.png)]] 139 139 140 T his analysis will enforce that the child tickets (usually found in a separate work queue report) are ordered relative to one another in the same general order as the parent/project tickets. To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows:140 To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows: 141 141 {{{ 142 142 [analyze] … … 163 163 }}} 164 164 165 In the example above, the project's 165 In the example above, the project's: 166 166 167 * effortfield sums all of its children numeric values168 * severityfield gets set to the minimum (index) value of its children169 * captainfield gets set to the most frequent captain of its children170 * phase pivots on the 'implementation'select option value167 * {{{effort}}} field sums all of its children numeric values 168 * {{{severity}}} field gets set to the minimum (index) value of its children 169 * {{{captain}}} field gets set to the most frequent captain of its children 170 * {{{phase}}} pivots on the "implementation" select option value 171 171 172 172 In brief, the pivot algorithm is as follows (using the option's index):