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

http://prntscr.com/gyd9co

Questions:

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?

Please note:

  1. Only time-tracking (effort expended) values roll up to the parent. Estimate (effort projected) values do not (and never will). 
  2. 'Parents' are only Stories or Tasks (or their cloned custom issue types).
  3. Time-tracking values only roll-up to their parent if the 'include-subtask' checkbox is checked in the Time-tracking widget on the 'edit page' of the Story or Task issue.
  4. There is a setting (somewhere) to make the 'include-sub-task' the default for time-tracking for Stories or Tasks... but I can never find it in the docs because the search engine for Jira Documentation is 'optimized' on words like 'roll up' to show only Portfolio issues.
  5. The explanation about why estimates will never 'roll-up' from sub-tasks is that the 'scrum purpose' for estimates and for time-tracking target different aspects of the scrum process (different scrum progress graphs). 
  6. If you are going to comment or inquire about this Jira behavior, please disambiguate your perspective to either 'estimation-only' or 'time-tracking-only' focus so that discussion of these topics can finally become sane and remain sane.

    thanks

Hi all, this is how I resolved this issue:

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

Hope this will be helpful! 

Screenshot-1.png

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 Don Sharp 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:

https://confluence.atlassian.com/display/JIRA/Configuring+Time+Tracking#ConfiguringTimeTracking-ConfiguringTimeTrackingSettings

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?

Nic Brough Community Leader May 31, 2018

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.

Like Marina Yantsevich likes this

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

Nic Brough Community Leader May 31, 2018

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 # people like this

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

Like Li Howe 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 # people like this

Gee, thanks for nothing. There is no "Time Tracking section".

Nic Brough Community Leader Jul 08, 2019

>Hey Nic would you be able to elaborate on why Atlassian thinks they are following the Scrum way by not doing this

In Scrum, an issue is done or it is not.  Partially done does not matter, did you deliver the issue or not?  Estimates on sub-tasks are utterly irrelevant to that question, because it doesn't matter if 0%, 1% or 99% of them are done - the issue is not done.

You burn down when an issue is done.  Not bits of it.

Nic Brough Community Leader Jul 08, 2019

>Gee, thanks for nothing. There is no "Time Tracking section".

Yes there is, if time tracking is enabled and in use in your project.  Have a closer look at the config.

Yes there is, if time tracking is enabled and in use in your project.  Have a closer look at the config.

 

There's a "Time Tracking" field, but it doesn't have any "Include sub-tasks" option.

>In Scrum, an issue is done or it is not.  Partially done does not matter, did you deliver >the issue or not?  Estimates on sub-tasks are utterly irrelevant to that question, because >it doesn't matter if 0%, 1% or 99% of them are done - the issue is not done.

>You burn down when an issue is done.  Not bits of it.

Thanks Nic. This explanation does help me understand the Jira approach to burn down charts. I completely agree with the Done or not Done, this is a core definition in scrum and with respect to summing up how many complexity points has been completed (velocity ) this makes perfect sense, but I have not found any definitions aout burndown charts must be based on danoe task only.

My experience as a scrum master is that the team has better use of tracking how many expected work hours is left in the sprint, and compare that to how many work hours is available. Bare in mind the expected work hours are still estimates. They are updated by the team whenever they get wiser and sometimes this may go up some times this may decrease. In both situations the team must consider the consequences and inform the PO if the sprint is on track or will fail. 

Hey Kristi, check out this question from a while back: https://answers.atlassian.com/questions/28328/jira-and-sub-tasksI 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
Community showcase
Published in Jira Software

Early Access: If you use Jenkins and Jira Software Cloud, you need to read this!

The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...

2,060 views 2 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you