Why doesn't the Backlog show the Estimate of all sub tasks?

For my stories in the Backlog (per sprint) that have estimates only on the Sub-Tasks there is no roll-up occurring on the display.  

It is fine if I view the Story itself, then it shows the summation of each sub-tasks original estimate.

Why is it not showing up in the Sprint yellow bubble or in the grey bubble along the Story row in the Backlog view?

2 answers

1 votes

JIRA doesn't expect you to estimate on sub-tasks.

It's a bit of a weakness, but the problem is that there's no consistent way to handle estimates on sub-tasks.  Do you roll it up to parents?  What if there's an estimate on the parent - add, remove or ignore?  How does it change the sprint if you're adding estimates to subtasks?  Atlassian have simply not dealt with it because there's too many ways you might try to do it, and no way to code for all of them.

Isn't this a similar situation to Story estimates being rolled into the Epic?  How is that handled?

No, because you don't estimate Epics either, so the rolling up is a simple case.

Estimates of sub tasks are rolling up in parent, if user open detail of parent. My Question is why its not appearing in backlog / scrum board.

I already said why it doesn't roll up.

The stuff you see on parent issues is rolling up estimates and worklogs for plain JIRA users, not Software.

Hello, it seems to me pretty simple solution.

I see two major scenario to use:

  1. when you use subtask estimation:
    * if story doesn't have any subtask you can estimate story
    * when you create first subtask estimation of story (loged time, remaining time) transfer to subtask, and after that you cannot change story estimation because now it's calculated from subtasks
  2. when you don't use subtask estimation:
    * let it work like now

If on board we can confugure this kind of behaviour, it'll solve problem.
it's very strange if i can estimate subtasks, but can't use it to build burndown chart. When I split my story to subtask, i'm going to assign different assignee, they can estimate subtask and actualize remaings most precisely.

And it's very strange to me, that you can't see the problem and ain't going to solve it.

Maybe there's some plugin, that recalculate story estimation based on subtask every time, it can solve our problem


any answer to this?  I am facing the same problem

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,965 views 12 18
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot