Agile Reports in Jira

[amy schneider]

Any guidance for reporting the correct data points for Burndown charts? Do these charts reflect both technical debt/defects and new feature requests/stories? Do the developerx really need to update this tool daily with their progress? Any tips would be appreciated.

[Kevin Bui · Accepted solution]

Hi @amy schneider - The Burndown chart in Jira relies on the estimates that are provided on each issue - estimates could be done using story points, or whichever metric you like. But yes, you could use it to report on both new feature work, and bugs too if you like.

As long as the developers are settings issues to the correct status (eg: To do, In progress, Done, etc...) as work progresses, the chart should provide insight into how the team is working.

If you want to learn more about how to use the Burndown chart, we have a guide about it here: https://www.atlassian.com/agile/tutorials/burndown-charts

If you want to learn more about how the Burndown chart works, you can check out our documentation on it: https://confluence.atlassian.com/jirasoftwarecloud/burndown-chart-777002653.html

For more information on estimations and story points: https://www.atlassian.com/agile/project-management/estimation

Hope that helps!

[amy schneider]

How can you report on defects by severity and by root cause in Jira?

[Kevin Bui]

Hi @amy schneider - Like many things in Jira, the answer is "however you want". It's a very flexible tool, so (for better or worse) it's up to each team to figure out how they want to do things. I recognize though that if you're new to Jira, this probably isn't very helpful so I'll try to provide some examples of how this might work.

One way you could do this is to report on defects using the Bug issue type - your dev team could raise a Bug every time a defect is discovered in the product. As for tracking root cause and severity, you could add a Root cause field and a Severity field to your bugs, so that every time a Bug is raised this must be filled out.

Another way you might accomplish this is to create a new issue type for Defects, separate to Bugs. The Defect issue type could have two custom fields that you add to it, Root cause and Severity.

Hope this helps!