Modify ↓
Opened 14 years ago
Closed 14 years ago
#9728 closed defect (invalid)
burndown chart broken with recent gviz libraries
| Reported by: | anonymous | Owned by: | Rob Guttman |
|---|---|---|---|
| Priority: | normal | Component: | SumStatsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.12 |
Description
The burndown chart was not displaying and I found the following javascript error:
"Bars series with value domain axis is not supported"
It appears the google vis library has changed, details here:
http://code.google.com/p/google-visualization-api-issues/issues/detail?id=795
I was able to resolve it by converting the dates to strings.
$ diff -u sumstatsplugin/0.12/sumstats/web_ui.py.orig sumstatsplugin/0.12/sumstats/web_ui.py
--- sumstatsplugin/0.12/sumstats/web_ui.py.orig 2012-01-25 12:49:58.000000000 -0500
+++ sumstatsplugin/0.12/sumstats/web_ui.py 2012-01-25 12:46:46.000000000 -0500
@@ -345,12 +345,12 @@
else:
total,done,todo = self._get_burndown_day(milestone, day)
# add to rows
- rows.append({'day':day, 'total':total, 'todo':todo, 'done':done})
+ rows.append({'day':day.date(), 'total':total, 'todo':todo, 'done':done})
day += timedelta(days=1)
# package the data for the google visualization query response
import gviz_api
- schema = {"day": ("date", "Day"),
+ schema = {"day": ("string", "Day"),
"total": ("number", "Total"),
"todo": ("number", "To Do"),
"done": ("number", "Done")}
Attachments (0)
Change History (4)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
As there is a workaround for this issue, I'm going to close as wontfix. If/when Google removes this deprecated functionality, I'll address at that time.
comment:3 Changed 14 years ago by
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
comment:4 Changed 14 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
Actually, this ticket should have been against the VisualizationPlugin, so marking as invalid for the SumStatsPlugin.
Note: See
TracTickets for help on using
tickets.



Yes, a bit frustrating that Google doesn't let you stick with prior versions! But this is actually a problem on the chart rendering/visualization side, not on this data provider side.
Another interim workaround for the visualization side is to use their newly documented
strictFirstColumnTypeoption. If using the VisualizationPlugin, for example:This should make the chart work with still using a continuous value for the (date) x-axis. But this is just an interim solution until I get around to a more robust, permanent solution for the VisualizationPlugin.