I'm using the statistic burndown chart with story points (daily). I have my version setup with multiple child versions (as my sprints). Since the project is quite large, I imported almost 500 issues with about 200+ of them being closed.They are in the current version I am trying to burndown. I've been closing stories but my burndown is almost flat and I cannot figure out why whatever I do doesn't impact the chart. Anyone have any ideas?
UPDATE: I should add that I have "released" all the old closed issues that I imported after adding them into child versions.
When you mention importing issues, it sounds like a problem I ran into. I finally found this other posted question and answers ...
https://answers.atlassian.com/questions/23524/issue-with-issue-burndown-chart
It sounds like, at least in some versions of these tools, that importing issues does not create sufficient history information to be able to produce correct burdown/up charts. There is a link to an Atlassian issue in the posting that provides a little more detail, but it was closed without fixing.
Don't know if this played a role in what you saw, but it makes sense for the problems I'm seeing. I've engaged Atlassian for help with this via ...
https://support.atlassian.com/browse/JSP-140369
It doesn't look promising so far.
Tom
Hi,
I ran into a similar problem a while ago and support confirmed, that greenhopper doesn't calculate the story points right if the child version dates aren't within the parent versions dates.
Example:
Parent: start at 10.9. end at 20.9.
Child: start at 15.9. end at 25.9.
As the child is not within the parent greenhopper messes up the story point count.
Hope this helps
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Motz,
Is your Burndown Chart based on number of issues because I believe it defaults to remaining hours.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my case, I created a dashboard and changed the default columns schema.
When I puted the last column with the status Cancelled the burndown chart stoped to show my sprint evolution, but, when I puted the last column with the status DONE the things gone back to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you add a screenshot of your Statistic Burndown Chart?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.