Does original estimate aggregate from subtasks to parent story in team-managed projects?

[Anna Laptyuhova]

Hi community,

I'm working in a team-managed Jira Software project with time estimation enabled (original estimate in hours).

Our current setup:

• Stories in the backlog
• Each story is broken into subtasks (Back / Front / QA)
• Original estimate is set on each subtask in hours

Expected behavior:
The sum of subtask estimates automatically rolls up and displays on the parent story.

Actual behavior:
The parent story shows no estimate — subtask values don't aggregate to the parent.

What I've already checked:

• Time estimation is enabled in Space Settings → Features
• Original estimate field is added to all work types including subtasks
• This is a team-managed project (not company-managed)

My question:
Is subtask-to-parent estimate aggregation supported in team-managed projects? If not, is there a recommended workaround that doesn't result in double-counting in reports (burndown, velocity)?

[Germán Morales _ Hiera]

Hi @Anna Laptyuhova , short answer: no. Subtask original estimates don't roll up to the parent in team-managed projects, and your configuration isn't the problem. That aggregate, the Σ that adds subtasks onto the parent, exists only in company-managed projects, and even there it is just a display in the time-tracking panel, not a value Jira writes into the story's Original Estimate field. Team-managed time tracking is the slimmer version and doesn't surface that roll-up at all, which is why your story stays blank.

The clean way to get a real total without double-counting is an automation rule: on a subtask created, edited or deleted, recalculate the sum of the subtasks' original estimates and write it to a separate number field on the story, say Subtask estimate total, while leaving the story's own Original Estimate empty. Keeping it in its own field is what avoids the double count, since your board's velocity and burndown read the estimation statistic you set at the story level, story points or time, and never pull from subtasks, so the two don't collide. Others have wired up exactly this, for example summing subtask estimates onto the parent with automation.

[Fatma Uzundemir from The Starware]

Hi @Anna Laptyuhova

This is expected behavior in team-managed Jira Software projects. Jira does not natively roll up Original Estimate values from subtasks to the parent issue, so the Story will not automatically display the total estimate.

If your goal is to keep estimates only on subtasks and automatically calculate the total value on the parent issue, you can use a calculated custom field solution like Sum Up Field.

Sum Up Field allows you to aggregate values from child issues and display the calculated result on the parent issue. You can select the field you want to calculate (for example Original Estimate, Story Points, or any numeric custom field) and choose the calculation method:

• SUM → Total of all child values
• AVERAGE → Average value of child issues
• MIN → Lowest value among child issues
• MAX → Highest value among child issues

               

🌱EXAMPLE:

Story
├── Backend Subtask → 5h
├── Frontend Subtask → 8h
└── QA Subtask → 3h

Using Sum Up Field (Original Estimate + SUM):

✔️ Story displays: 16h

The value is dynamically calculated, so any change in subtask estimates is automatically reflected on the parent issue.

This also avoids maintaining estimates in two places (parent + subtasks), helping prevent duplicated effort calculations and keeping reports like burndown and velocity more consistent.

Sum Up Field can be used not only for estimation scenarios but also for different Jira numeric fields and custom fields where you need automatic roll-up calculations across your issue hierarchy.

🍀 To learn more, feel free to contact me or explore the application through the Atlassian Marketplace link I’ve provided. 🍀
Disclaimer: I work for the vendor who developed this application.

[Rahul_RVS]

Hi  @Anna Laptyuhova 

For rolling up time tracking values to parent, if you are open to try out a mktplace app, take a look at,

Agile Tools

The app allows you to view your issues in a hierarchy list view with roll up of time tracking data at Epic level and at each parent level.

The hierarchy works for issue links as well with the Links Hierarchy module of the app. All the app features can be added as gadgets to a dashboard.

Do give it a try.

Disclaimer : I am one of the app team member