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

Time Spent roll-up from Story/Task subtasks to Epic

Gor Greyan

Hi Community,

We have the following Jira Cloud hierarchy:
Epic
└── Story / Task
├── BE Sub-task
├── FE Sub-task
└── QA Sub-task

Our users log time mainly on the Story/Task subtasks.

On the Story/Task level, Σ Time Spent correctly includes the time logged on its subtasks. However, at the Epic level, the Time Tracking field does not recursively roll up all time from the Stories/Tasks and their subtasks.

For example.

Epic
└── Story A
├── BE Sub-task → 10h
├── FE Sub-task → 5h
└── QA Sub-task → 3h

Expected Epic total → 18h

I know we can implement a workaround using Jira Automation, JMWE, or a custom field to calculate the total.

However, before implementing a custom solution, I'd like to confirm:

Is there any native Jira Cloud configuration that can recursively roll up Time Spent from Epic → Story/Task → Sub-task?
Is there another recommended solution that doesn't require Automation/custom fields?
I found https://jira.atlassian.com/browse/JRACLOUD-93508. Is this still the relevant Atlassian ticket to follow for this requirement, or is there a newer feature request/bug tracking it?

Would be interested to know how other organizations handle this.

Regards,
Gor

Accepted answers

Tomislav Tobijas

Hi @Gor Greyan ,

Last year I was implementing a solution for this, but apart from automating things, there's not much you can do. There was this discussion that you can take a look at 👀 and also this feature request JRACLOUD-70150: Sub-tasks no longer have their estimate and time tracked on the parent (Epic) issue for the new Full View Issue experience, which is partially related to what you're looking for.

Apart from this, I've seen customers using third-party reporting tools (e.g. PBI) to display these roll-ups/sums and not to do calculations within Jira itself.

But if anyone has found any other solution, that would be cool to hear.

Cheers,
Tobi

Habib__Plugio__

Hi @Gor Greyan

No native setting does this. The time tracking roll-up is one level only, by design. Atlassian says so in the June 2025 update on JRACLOUD-70150: a sub-task rolls up to its parent, and the Epic gets its direct children, but nothing from the sub-task level. "Include subtasks" on the Epic doesn't change that.

JRACLOUD-93508 is still the right ticket. It describes exactly your case and is open in "Gathering Interest" with 5 votes. I couldn't find a newer one that replaces it. JRACLOUD-70150 is the older, broader one with 378 votes, so I'd watch both.

Without Automation or a custom field, the remaining option is to calculate the total at view time. Disclosure: I work at Plugio, and our app Plugio Panels is one way to do that. It adds a panel to the Epic that sums Time Spent over "Full hierarchy", meaning the children and their sub-tasks. It reads each work item's own Time Spent, so sub-task hours aren't counted twice. Your example would show 18h. The total is display-only. Nothing is stored, so you can't use it in JQL or reports.

All comments

Tomislav Tobijas

Hi @Gor Greyan ,

Apart from this, I've seen customers using third-party reporting tools (e.g. PBI) to display these roll-ups/sums and not to do calculations within Jira itself.

But if anyone has found any other solution, that would be cool to hear.

Cheers,
Tobi

Habib__Plugio__

Hi @Gor Greyan

Gor Greyan

Hi @Habib__Plugio__,

Thanks for the detailed answer and for confirming that JRACLOUD-93508 is still the relevant ticket.

For now, we'd prefer not to introduce an additional paid app just for this requirement. Since there is no native solution, we'll most likely handle the roll-up using Automation or our existing customization options.

Thanks again for clarifying the native behavior and sharing the alternatives!

Gor Greyan

Hi @Tomislav Tobijas,

Thanks for sharing your experience and the related discussion/ticket, Tobi.

It looks like Automation is the most practical option for us as well. We would prefer to keep the calculation within Jira rather than introduce a third-party reporting tool just for this roll-up.

Hopefully Atlassian will eventually provide native full-hierarchy time tracking roll-up.

Thanks again!

Regards,
Gor

Danut M _StonikByte_

Hi @Gor Greyan,

Since you asked for a solution that doesn’t rely on automation or custom fields, another option would be to explore apps available on the Atlassian Marketplace.

If you’re open to using an app and you need this for reporting or tracking purposes, I’d recommend taking a look at the Pivot Table & Pivot Chart gadget, available in our Great Gadgets app. This gadget allows you to display the issues from your epic along with the time spent, including time logged on sub-tasks.

For your use case, it should be configured like this:

Hope this helps.

Danut.

Gor Greyan

Hi @Danut M _StonikByte_,

Thanks for the introduction of the app,

For now, we'd prefer not to introduce an additional paid app just for this requirement.

Most probably will implement with the custom solution.

Thanks again.

Regards,
Gor

Welcome!

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

Quick Links

Find more posts tagged with

jira

epic

timespent

rollup