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; } } }

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

kristi kuykenda

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.

Accepted answers

All comments

Andrew Wolpers

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.

Charles Wells

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.

kristi kuykenda

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?

Charles Wells

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?

kristi kuykenda

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.

Joseph Syjuco

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?

Andrii Kratik

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?

Lutz_Pliske

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

Ivan Tkachenko

Hi all, this is how I resolved this issue:

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

Hope this will be helpful!

Kadamb.Thakkar

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"

aviv hadar_njizbr

I also need this. Thanks

Kimball Johnson

Please note:

Only time-tracking (effort expended) values roll up to the parent. Estimate (effort projected) values do not (and never will).
'Parents' are only Stories or Tasks (or their cloned custom issue types).
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.
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.
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).
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

Arun_Thundyill_Saseendran

The link is defunct.

Tony Clarke_tf297q

I believe this is the new link:

https://community.atlassian.com/t5/Jira-questions/Jira-and-sub-tasks/qaq-p/56934

Erik Sternå

This worked for me and was exactly what I wanted. I had only "Remaining estimate", rather than "Σ Remaining estimate", which meant the time estimate of tasks showed up, but not the summary. Once I exchanged them, it worked well. Thank you!

AKBAR_vb5daf

@Erik Sternå,

Good day.

Please can you explain a bit in detail?

Shall I add "Σ Remaining estimate" field on to the Issue screen to view it accumulated?

Thanks in advance.

Regards,

Akbar.

Anthony Jasicki

Hello,

My solution for push-up the Original Estimate of Sub Tasks in parent Task :

With plugin : Script Runner
Create : Script Listeners
Set on these event : Task Update, Task Create
/!\Important/!\ Set on user : ScriptRunner Add-on User

And Copy & Paste this code :

if (!issue.fields.issuetype.subtask) { 
return
}

// Retrieve all the subtasks of this issue's parent


def parentKey = issue.fields.parent.key
def allSubtasks = get("/rest/api/2/search")
.queryString("jql", "parent=${parentKey}")
.queryString("fields", "parent,timeestimate")
.asObject(Map)
.body
.issues as List<Map>
logger.info("Total subtasks for ${parentKey}: ${allSubtasks.size()}")

// Sum the estimates
def estimate = allSubtasks.collect { Map subtask ->
subtask.fields.timeestimate ?: 0 
}.sum()
logger.info("Summed estimate: ${estimate}")


// Now update the parent issue
int estimateHours = estimate / 60 / 60

logger.info("Parent Issue: ${parentKey}")
logger.info("Summed estimate in hours: ${estimateHours}")


put("/rest/api/2/issue/${parentKey}") 
.queryString("overrideScreenSecurity", true)
.header("Content-Type", "application/json")
.body([
fields: [
timetracking: [
originalEstimate: estimateHours
]
]
])
.asString()

That's work

Anthony,

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration

time-tracking