Analyzing Bugs vs. Stories in Jira Burndown Chart

[Patrick Woodward]

I'd like to filter bugs only, or stories only, in my Jira burndown chart.  Is there a way to filter/ sort this way so I can track progress of each category (bugs / stories)?

[Raimundas Juska · Accepted solution]

Hi,

You can try this app that I have created for this purpose, it allows you to filter data via JQL filter (issuetype = story) - https://marketplace.atlassian.com/apps/1219872/advanced-burndown-chart-gadget-for-jira

[Patrick Woodward]

Got it.  Thank you!

[Антон Клочихин]

Jira draws Burndown chart when tasks moves into status Closed. In my project, there is an additional status Ready for release
Tasks could being in this status (Ready for release) for a week
(this is tasks that have already been tested, but not yet deployed on Production server).
Accordingly, Burndown chart does not display real progress of team.
Could you tell me, is it possible by using your app to draw Burndown chart in Jira by the status of Ready for release, and not Closed?

[Raimundas Juska]

No, unfortunately tasks are only burned when they are resolved, not moved into some custom status.

[Ollie Guan]

Hi @Patrick Woodward ,

I think the burndown chart is used to track the progress of all Backlogs included in a sprint, not a specific Issue type.

You can use other dadget in the dashboard to track the progress of bugs.

Hope it helps.

[Natalie Paramonova _Stiltsoft_]

Hi,

You can use the Table Filter and Charts app to build a burndown chart in Confluence. The app provides a flexible configuration so you can filter any issue types. You can find the instructions on the documentation site.