Release Burndown

[Giri Narayanan]

From the documentation on Release Burndown available in https://confluence.atlassian.com/agile/jira-agile-user-s-guide/using-a-board/using-reports/viewing-the-release-burndown, I understand that it is through version that the Release burndown chart is maintained in Jira and there is no ‘Release’ entity. Is it possible to generate the report at the release level (eg Release 1 comprising of sprint1,sprint2,Sprint3).

Given that the workitems(i.e User stories) are likely to delivered across different internal releases (as part of their respective sprints internally), they will be holding different Fixed Build number. Wanted to check with you on any recommended approach in this context so as to generate the Release Burn Down Report covering Sprint1,sprint2,Sprint3 User stories

[Danut M _StonikByte_]

Hi Giri. Try the Great Gadgets add-on:

• Jira Cloud: https://marketplace.atlassian.com/plugins/com.stonikbyte.great.gadgets.plugin/cloud/overview.
• Jira Server: https://marketplace.atlassian.com/apps/1218777/great-gadgets-for-jira-server?hosting=server&tab=overview

It offers a Release 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 can be done by Story Points, Issue Count or Original Time Estimate.

See more details here: https://bitbucket.org/StonikByte/great-gadgets-add-on/wiki/Home