How to show when work is added using the statistics burndown chart?

[Mark McD]

I am using the statistics burndown chart to show the burn down of story points over my entire product backlog, running from say Jan 1 to Feb 28.

When I add a new story of 5 points value on January 30, the story points seem to be added to the very start of the burndown chart, adding 5 points to every data point in the chart. This causes my reports to be misleading, as it depicts the value as always being present. I would like to show that on Jan 30, 5 points were added to the backlog.

I assume I have configured the chart incorrectly somehow, as the other burndown charts (i.e. hour, issue) will create a "spike" when the value increases.

How can I configure my statistics burndown chart to increase when data is added?

[Edwin Stol]

Thanks for your reply Mark; i've looked into the Rapid Board as well, and noticed that works as expected. We should start using this then, since it's the 'future of Greenhopper'.

[Edwin Stol]

Im curious to this as well; i am experiencing the same problem.

Mark; did you manage to resolve this issue?

[Mark McD]

No I did not. It seems that GreenHopper will take the "created" date & use that. If the created date is within the sprint, then it will bump, if it's before then the whole chart goes up.

What you may find useful is the latest GreenHopper release (5.9.7.3 at time of writing) has a beta feature in the Rapid Board for pure-scrum teams, where it tracks scope creep as you would expect it to. Check it out here: https://confluence.atlassian.com/display/GH/Viewing+the+Burndown+Chart