Earn badges and make progress
You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Why does the 'Progress (story points)' field include sub-tasks in the unestimated metric?
Edited
When calculating the Unestimated issues metric, the Progress (story points) field takes into account standard issues and sub-tasks.
In the example below, you can see that I have three standard issues under the Test Epic 1. All three have been estimated. And yet the Unestimated Issues field indicates I still have 3 unestimated issues.
One of the unestimated issues is the epic itself. The other two are unestimated sub-tasks under Test Story #1.
Almost every team I've worked with estimates product backlog items but not sub-tasks, so it's very unfortunate those are factored into the Unestimated issues metric. Is there a method to remove sub-tasks from being calculated in this metric?
Also, it seems like the Unestimated issues may just be buggy given that the Progress (issues) field only shows 3 issues. It does not factor in the epic itself or sub-tasks, which is how I would expect a progress metric to be calculated given that's how 90%+ of teams work.
