I am resolving this issue as completed, as we have implemented real time burndown charts in the new Agile boards.

We will not be improving the Classic burndown charts to also be real time.

Regards,
JIRA Agile Team

Agreed, hours are what the burndown chart calls for in the vast majority of literature, and I presume it's what the vast majority of teams use. We would not accept anything else. Story point burndown is for the release burndown chart, not the sprint burndown chart.

If, of course, the rapid board gets the expected hours burndown capability, and then a new dashboard gadget follows that, then voila, we've probably got a perfectly workable solution and happy-go-lucky users.

I'm all for moving forward with the rapid board when it's ready. But I tried playing with the scrum rapid board, and, as of 5mar12, I got stuck pretty quickly on what appears to be unfinished functionality that sent me crying to support.

I also agree that the priority of this issue is too low. We want our burndown chart posted on a wallboard display in the office, but not in its current form. Most scrum literature calls for "information radiators" to be posted pretty much everywhere possible, with the sprint burndown chart usually being the first such "information radiator" mentioned.

Thanks Shaun for the advice,
However I recently did an investigation how burning down hours compares to story points and remaining tasks. From my perspective during sprints I recommend burning hours or for experienced teams burning down tasks because it shows that the shape of the burndowns is actually pretty simular. Burning down story points however is much to coarse grained and too inaccurare for a timely feedback for the team.

Having said that: Is it possible to show the issue burndown instead the story point burndown within the burndown charts for the rapid board?

=Stefan=

You might like to check out the new Burn Down charts included with the Rapid Board for Scrum (which is in labs). It currently only burns down story points but it is real time. We intend on significantly enhancing the Rapid Board charting moving forward and will then integrate it in to the Agile Gadget.

Thanks,
Shaun

I can very much second what David is saying. It shouldn't be hard to fix but is pretty important to be done. I cannot see why it is ranked "minor". We are using Jira throughout our woldwide company and almost anyone is complaining about that.

We very much agree here and were about to create the same request.

The 'Hour Burndown Chart' dashboard gadget only shows burndown data that has completed. Essentially this is a one business day lag.

This is way too slow for Agile development. Imagine a sprint length of 1 week, one business day behind is 20% of the whole sprint, that's way out of date. Even the typical 2 week sprint cycle is a 10% lag, that's huge, and makes the gadget virtually useless.

We need to see how we are currently doing against our goal. The dashboard gadget really needs to plot all available data. Even though the most recent day is in flux (the dashboard gadget does include an auto refresh option anyway).

At least this option needs to be available. As-is, the dashboard burndown gadget is just too far out of date to be useful.

currently i just see a hours burndown gadget but no issue burndown gadget. How can we get an issue burndown gadget on a wallboard?

The wallboard gadget should show the current day's burndown as well.
I like how the non-wallboard burndown chart widget has the dotted line portion for the day in progress. For the wallboard gadget, it would also be nice to see gray axes and a couple labels instead of the "ideal" guideline which is not really very useful in any of the charts.