The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Tempo Time Spent not aggregating from sub-tasks

Andres Oss
Contributor
May 27, 2025

Tempo isn’t currently aggregating Time Spent from sub-tasks.
When we open an Epic, we expect the total to include hours logged on its sub-tasks, its parent tasks, and the Epic itself. Right now, the total is incorrect—it only adds up hours from the Epic and its direct tasks.

We see the same problem in Confluence pages that display Jira issue lists: the Time Spent column doesn’t sum the hours as expected.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Dmitry Astapkovich _Colined_
Atlassian Partner
May 30, 2025

This is one of the biggest reasons we have Pivot Report customers, who using Tempo. 

SCR-20250530-mpmr.png

 

On top of stand alone report, we have two customizable widgets for Issue/Work item view: Issue Tree and Issue Progress. You can define if you want all work items to be calculated for totals, or only so called "leaf nodes":

SCR-20250530-mqty.png



SCR-20250530-mrmy.png

Andres Oss
Contributor
June 4, 2025

It looks good, although it is another extra expense for the Jira setup.
Tempo should inherently have such configuration properties available.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events