It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I get a parent issue to include hours estimates from the sub tasks?

How do I get a parent issue to include hours estimates from the sub tasks? May parent task has 0 hours but the subtasks have original hours estimates. The parent issue should reflect the hours of the subtasks.

5 answers

Not sure if this has been resolved already but I am running into the same issue.  I have the ff.

- 1 Story with blank estimate

- 2 subtasks underneath with 1 day each

- When I check Version Report, the Story still reflects as unestimated

I was expecting the subtasks are rolled up to the parent which means the parent story is actually estimated.  When both subtasks are closed with 0d left, it should reflect in Version Report (which is not happening).  Is there a way to use the ∑ Original Estimate when creating Version Report?

the same situation

in Backlog view the estimation of subtasks is not included to parent task estimation and total number of hours in sprint - as a result unable to plan sprint based on this number (subtasks not included)

Burndown report does not include subtasks estimate


1) how to include subtasks estimate to total parent task estimate so it' counted in Backlog view?

2) how to include subtasks estimate to Burndown report?

Same here. Is there anybody from atlassian helping on this issue?

Hi all, this is how I resolved this issue:

Board Settings -> Card layout -> Choose 'Σ Original Estimate' / 'Σ Remaining Estimate'

Hope this will be helpful! 


Try this...

Guess you have only one sub task in Story. Original estimate of sub task was 5 hrs...someone went in and logged hours as 2 but remaining hours was changed it to 4 (instead of 3).  Now try to see the "Actual remaining hours" using your data . It will never say "4"

Hi Kristi, go to the Time Tracking section of your parent issue and check the box for "Include sub-tasks".

This will aggregate all estimates and logged work from sub-tasks to your parent issue.

I checked the "include sub-tasks" but the hours estimate still shows as blank when planning a sprint as well as the version report. I have my hours estimates in Original Hours Estimate. Should I have it some where else?

Like 1 person likes this

That functionality exists as part of the base Time Tracking. I'm unable to paste in a screenshot, but it shows under the three bars (Original Estimate, Logged, Remaining Estimate). I'm not aware of a specific configuration for it. The latest documentation can be found here:

Can you provide any other details that may help?

I want to see the cumulative hours on the parent ticket in the issues list in Plan mode. Currently I only see hours associated with issues that have been specifically assigned an estimate so a parent issue with subtasks will not display an hours estimate when viewing the list.

I´m in the same situation...Is there any solution to this issue?

is this resolved? If so can someone post a screenshot where we do this?

It has never been a problem in plain Jira (Different story if you're using estimates in Software)

All parent issues have a panel where you can toggle the timetracking view between "this issue only" and "this issue and all its subtasks"

Since Jira 3.something, you've been able to use Σ fields in the issue navigator to display the sums in columns too.

in issues > all issues i can see this.

How can i view this in the backlog? My subtasks times are not updated within the parent

Ah, now you've run into the problems with sub-tasks in Jira Software.  Atlassian are sticking to the way Scrum is done, where estimates on sub-tasks are irrelevant to the backlog and burn-down, and there's no roll-up to parents.

Like 1 person likes this

This seems nuts to me, we don't all work in Scrum. 

Like 1 person likes this

Hey Nic would you be able to elaborate on why Atlassian thinks they are following the Scrum way by not doing this?  Hopefully this can help me understand better why I am struggeling with time registration and ruff burndowns which does not help the team.

Based on the SCrum guide, there is nothing called sub-task ;) of-cause. But what anoys me the most is that Jira does not help the team manage their remaining estimates.

(ref The Scrum guide chapter on Sprint Backlog)

I am use to that the team can easily look at the burndown and see. This is how many hours we estimated for all the sub-tasks left in the sprint, and this is how many hours we have available (- some people are out of the house, doing urgent stuff or sick ) 
And  they they can react if they to low or too high.

But Jira does not help met gather this information in the burndown and as I can understand on your reply, they dont seam to bother about it :(

Like 3 people like this

Hey Kristi, check out this question from a while back: believe the discussion in the comments will help clarify things.

0 votes

I also need this. Thanks

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

1,107 views 1 13
Read article

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