How does JIRA count unestimated issues for the Release Burndown?

For the life of me I can't understand how JIRA counts the number of unestimated issues in order to calculate the % of issues that aren't estimated.

For example, I'm looking at my Release Burndown report for Release 1.0 and it says '12% unestimated issues'. I hover my mouse of that label and it says '12% of issues do not have an estimate (31 of 261)'. However, when I scroll down to see all of the stories in each sprint there are only 18 that don't have story points, not 31.

Why does JIRA think there are 31?

I've read the documentation (https://confluence.atlassian.com/display/AGILE/Viewing+the+Release+Burndown) 20 times but haven't found the answer.

Thanks.

1 answer

I think JIRA takes into account all issues without story points in the epic, including already closed ones (it can be either fixed issue or closed as Duplicate...).

So when JIRA says (31 of 261), but you see just 18 unestimated issues, I think there are 13 ones which has already been closed without estimation.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

24,163 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you