Release Burndown Chart

[Ernie Varitimos]

I'm new to Atlassian development and need direction on how to create a burndown chart that encompasses an entire release.

I have searched for ways to do it with workarounds on the current sprint-based burndown gadget, but nobody seems to have an answer, so it looks like development is the next path, however I need some direction.

Can you point me to a person that can help?

-ernie

[Danut M _StonikByte_]

Try the Great Gadgets add-on for JIRA cloud (https://marketplace.atlassian.com/plugins/com.stonikbyte.great.gadgets.plugin/cloud/overview). It offers a Release Burnup Burndown Chart gadget that is based on a JIRA filter. Put in that filter the issues from your project scope and group data by your sprint duration and you will have the burndown chart. Calculation is done by Story Points field.

See more details and other useful gadgets (like Team Velocity chart) here: https://bitbucket.org/StonikByte/great-gadgets-add-on/wiki/Home

Danut.

[boardtc]

It's frustrating, the release burndown report is misnamed as it does not show a burndown chart and also the filter can't be changed  Older versions of JIRA had the sprint burndown gadget which ran against a filter, removing that was a backwards step 

[David Ross]

There are two gadgets within JIRA that will achieve what you are looking for:

1) Release Burndown:  https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-a-board/using-reports/viewing-the-release-burndown

2) Version Report:  https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-a-board/using-reports/viewing-the-version-report

These are similar, but show the same information in slightly different ways.  We use these extensively in our organization.  Both reports can be generated in JIRA, but only the Version Report is available as a gadget in Confluence (if you want to create a separate Confluence page to track this information).   Hope this helps.  

[Owais Ashraf]

I am totally amazed, there are several requirements of Agile that JIRA doesn't fullfil. After all it is just an issue management system that is stratigically converted into agile. Release burndown is a common but most important illustration for Agile Project that JIRA doesn't offer. It provides no help to management when you want to track progress of multiple projects at a same time. The pace of improvements JIRA is making is very poor indeed. It seems like they will take years to produce something useful and still they will ask you to buy addin which is of less use.

[francis]

Hello Ernie, we have the same issue.
Did you find/developped a solution ?