Changes between Version 21 and Version 22 of SumStatsPlugin


Ignore:
Timestamp:
Jan 3, 2012 4:09:16 AM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SumStatsPlugin

    v21 v22  
    112112[[Image(burndown.png)]] 
    113113 
    114 The data source reuses the {{{filter}}} option set in the {{{[sumstats]}}} section.  See step 4 of the [wiki:SumStatsPlugin#Configuration Configuration section above] for more details.  No additional configuration is required to enable the burndown data source.  It is accessed at: 
     114The data source reuses the {{{filter}}} option set in the {{{[sumstats]}}} section.  See step 4 of the [wiki:SumStatsPlugin#Configuration Configuration section above] for more details.  No additional configuration is required to enable the burndown data source.  However, it currently makes the following assumptions: 
     115 
     116 * "done" means closed as {{{fixed}}} 
     117 * if a sum field is provided, then it's assumed to be a custom field (not a standard field) 
     118 * if the milestone cannot be extracted from the referrer url, then the current milestone is assumed. 
     119 
     120The data is accessed at: 
    115121 
    116122 http://<your-trac-domain>/sumstats/query 
     
    129135Only the select phrase is used at this time to specify which columns to return and their order.  The {{{day}}} field is always the first column and should be omitted from the select phrase.  You may need to urlencode the {{{tq}}} value. 
    130136 
    131 Let me know if you need additional flexibility in the query and I'll consider adding it. 
     137Let me know if you need additional flexibility in the query and I'll consider adding it (e.g., specifying the milestone explicitly, a different timeframe grouping than daily, etc.). 
    132138 
    133139== Recent Changes ==