Changes between Version 21 and Version 22 of SumStatsPlugin

Timestamp:

Jan 3, 2012, 3:09:16 AM (12 years ago)

Author:

Rob Guttman

Comment:

--

SumStatsPlugin

@@ -112 +112 @@
 [[Image(burndown.png)]]
 
-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:
+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.  However, it currently makes the following assumptions:
+
+ * "done" means closed as {{{fixed}}}
+ * if a sum field is provided, then it's assumed to be a custom field (not a standard field)
+ * if the milestone cannot be extracted from the referrer url, then the current milestone is assumed.
+
+The data is accessed at:
 
  http://<your-trac-domain>/sumstats/query
@@ -129 +135 @@
 Only 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.
 
-Let me know if you need additional flexibility in the query and I'll consider adding it.
+Let 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.).
 
 == Recent Changes ==