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
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I tried looking for methodology docs without luck on this topic. I'm generally curious about what comprises "Unestimated Issues" in Advanced Roadmaps when you hover over "Progress(Story Points), as well as the extent of customizability.
For example, which issue types are included by default? (story/tasks/bugs? Epics? Sub-tasks? All the above?) If there are unestimated issues under a resolved epic, do those count? If the issue itself is resolved but unestimated, does that count? How do you customize what counts as "unestimated"?
It seems like a helpful feature, but I'm not comfortable using it in reports until we confirm the logic and extent of its customization. Thanks in advance!
It's good that all descendent issues in the plan are considered, but the implementation is flawed. If the Estimation statistic is set to Story Points, "unestimated issues" includes sub-tasks which do not have a Story Point field. The list of descendants should be Qualified descendants only, i.e. those that can be estimated using the selected estimation statistic.
I'm a little confused about this... you can add story point estimates to sub-tasks (both within Advanced Roadmaps and directly on the issue details screen as far as I can tell).
See screenshot for an example, the issue DP-7 is a sub-task of DP-2
It can be configured that way, but typically is not. In our case the field is neither present on the screen nor in context for the issue type. Therefore it is not possible for these issues to *ever* be "estimated" using the preferred statistic. BTW we use Jira server.