nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Marty Berryman

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?

Accepted answers

All comments

Noor Muhammad1

any answer to this? I am facing the same problem

Nic Brough -Adaptavist-

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.

Marty Berryman

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

Nic Brough -Adaptavist-

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

Noor Muhammad1

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.

Sanwar Mal

Gosh! Atlassian.

you can add up the subtask estimation to parent on view issue(Parent) screen but not to backlog estimation.

You have an option board to exclude sub-task but to to include. I am feeling dumb now to choose JIRA. Mind that i have a 2000 user license. and cribbing here on community.

Stupid me!

Nic Brough -Adaptavist-

Mmm, it's the same answer as above - there's lots of schemes you might use, you don't want to annoy existing users by pulling their scheme out from under them, and you shouldn't estimate at sub-task level in scrum, as it's pointless.

Sanwar Mal

Thank you ! I don't see a point discussing here, will try to negotiate my license renewal next time.

The "Σ Original Estimate" field will show the sum of estimates of all subtasks and the parent item. This can be inserted as a field into the Backlog cards view but note you cannot search for the field, you must go to the bottom of the list to pick it.

This summation Estimate value does not get reflected in the summed estimates from the "Workload by assignee" pop-up in the Backlog, which still omits any sub-task estimates.

To get a view of estimates by Assignee including subtasks, I copied my existing board filter and added column for Σ Original Estimate. I add a filter to exclude Sub-tasks from results so subtask estimates don't get counted twice.

Many have asked for the Sub-task estimate roll-up to be added as a core feature, but it hasn't been prioritized. You can get it in Portfolio, or in a paid add-on, but still would be nice to have it standard.

Theen-Theen Tan

What is the paid add-on you are referring to? Atlassian, want rolled out hours estimates in Backlog view for stories!

Theen-Theen Tan

What an I do this:

"This can be inserted as a field into the Backlog cards view but note you cannot search for the field, you must go to the bottom of the list to pick it."

When I said "paid add-on" I meant using a general-purpose tool like ScriptRunner, which I believe is capable of custom queries more like SQL that include sums/math functions and inserting results into different views?

As far as I know, there is no paid (or free) add-on which specifically addresses just this one issue of subtask summation.

Inserting the "Σ Original Estimate" field into Backlog cards view - this is just going to the Board settings > "Card Layout", scroll down to the bottom of the dropdown and find "Σ Original Estimate" to set as one of the 3 extra fields allowed.

Even with this approach we've since moved off of using Sub-Tasks as we found too many other limitations which we wish could be configurable to be a bit more like Tasks in some ways. Instead we now use Tasks linked to other Tasks which has not great UX (clutter etc), but still better overall for our workflow.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud