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?
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 (126.96.36.199 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
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot