Changes between Version 35 and Version 36 of AnalyzePlugin


Ignore:
Timestamp:
Apr 9, 2012, 3:56:58 AM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnalyzePlugin

    v35 v36  
    138138[[Image(rollup-project.png)]]
    139139
    140 This 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:
     140To enable this analysis for a given report, list those reports in {{{trac.ini}}} as follows:
    141141{{{
    142142[analyze]
     
    163163 }}}
    164164
    165 In the example above, the project's
     165In the example above, the project's:
    166166   
    167  * 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
     167 * {{{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
    171171
    172172In brief, the pivot algorithm is as follows (using the option's index):