Burndown chart by storypoints on issue status other than closed?

[grant luna]

Currently, the Greenhopper "statistics burndown chart" by "story points" considers an issue "burned" if the issue has a status of "closed" (this is my understaning of how it works). Can this be changed to burn down story points on a different issue status? Or multiple issue status? I want to chart issue burn down when the issue status is "ready for UAT" or "closed".

[Nicholas Muldoon · Accepted solution]

See response here:

http://confluence.atlassian.com/display/GH/Viewing+the+Statistics+Burndown+Chart?focusedCommentId=277252903&#comment-277252903

[Chris_Green]

404 - Page Not Found

[Chris_Green]

@Nicholas Muldoon do you have an updated link please?

[Benjamin Klein]

https://confluence.atlassian.com/agile064/jira-agile-user-s-guide/using-the-classic-boards/using-the-classic-chart-board/viewing-the-statistics-burndown-chart

[Midori]

If you need more fields or other fields than status to represent "DONE" or you have a totally different definition of "DONE", you may want to implement a custom agile report with JIRA PDF View Plugin.

You can use the default Burn Down Chart template and customize the logic in the init() method of "burn-down-chart.groovy".

...
if(it.resolutionDate != null) {
                    tasksDone++
...

It, by default, considers any issue done if its resolution date is not null. (We got this request in an agile Requirement Management context.)

[Korayem]

We've solved this: during a sprint, the team updates Story Points field by reducing (or increasing) its value to what they see as remaining. This makes the chart burn down :)

[Salem Korayem]

We've solved this: during the sprint, the team updates Story Points field on parent issue by asking "how much points are their remaining?" resulting in points reduction or increase. This makes the chart burn down though the issue is still in progress :)