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

Tempo: Parent issue rollup report

Paul Alexander

Tempo team - Why is there no parent issue roll-up report in the product yet? For instance, I can run a report and filter the rows displayed by 1) Projects, 2) Activities, 3) Issues, or 4) Worklogs. #1 and #2 are too high level. #4 has too much detail. And #3 rolls up to subtasks (example below), but not even the name of the parent is visible. To get a report in front of the business people, we need to show them the list of parent issues; they could care less about the subtasks it takes to perform the work.

What are others doing to compensate? Or better yet, what's the ETA from Tempo for this very basic need?

//This is what we get today that does not work (filtering rows=Issues)

JiraProjectKey - JiraProjectName

JiraProjectKey - Version

JiraParentIssueKey / JiraSubtaskIssueKey JiraSubtaskIssueSummary JiraSubtaskIssueTimeSpent

//This is what we need (filtering rows=Parent Issues)

JiraProjectKey - JiraProjectName

JiraProjectKey - Version

JiraParentIssueKey / JiraParentIssueSummary JiraParentIssueSumOfTimeSpent

Accepted answers

All comments

Paul Alexander

Tempo team? Anything?

Yesterday, I had to release a customer billing report by a) providing the Tempo report by subtasks and then b) also including a table result set of a search to provide the titles of the parent issues. Together, the customer is going to have to mind map the two documents to understand what we did. This is stupid...

Birgir Snævarr

Hi Paul

After conferring with the Tempo Timesheet product owner I can tell you that this is not on the immediate roadmap.

Tempo is always looking to to improve the reporting within Timesheets and the product manager would like to get further information regarding your case and suggested that you take a look at an issue that is logged in our external Jira that touches on the same issue that you are facing. The product owners monitor those issues so this could be a excellent channel for you to get your ideas directly to them

The link to the issue is: https://tempoplugin.jira.com/browse/TT-81

Best regards,

Birgir Asthorsson

Paul Alexander

Tempo user community - What are you doing in your world to produce a report by parent issue? At this point, I can't believe this simple report demand cannot be yielded. Help me out someone. Big thanks.

Here is an example of what I need, and assume all of us need, right?

Matthias Kannenberg_srqado

I second that this is a very reasonable request and we are missing this feature, too.. For the moment, we help us with using JIRA Structure to create an Epic -> Story > SubTask overview and let all the spent time accumulate.. But this is only half the way because this is always overall time and not a time frame like per month or per sprint.

Paul Alexander

I still cannot believe you and I, Matthias, are the only people affected by this. Without this report structure, I cannot justify paying this kind of money every year for Tempo...I just can't... sad .

Samuel Levine_ptuqxx

Is there another product that Atlassian provides that does this roll-up of all user stories/sub-tasks to the Epic level?

Carl Denault

The link above : https://tempoplugin.jira.com/browse/TT-81

Seems to not work anymore. Is there any update on this issue? Our company would love also this feature to be in tempo Custom Report.

Our workaround for now is to explain all the Epics / Story / Subtask in the subtask section in JIRA

So in Tempo, the name looks like this in our report --> Epics Name ***This is a story*** Here is the subtask

Weird we are now in 2019 and there is no solution for this issue.

Best Regards,

Christian Friede

We're facing the same Problem and solved it with ScriptRunner plugin:

1. Create a new jql query like: issueFunction in subtasksOf("Epic Link = <your Epic ID>")

2. Save it as Filter

3. Got to Tempo Reports. Create new "Jira Filter Report" and pick your saved filter

4. Group and display your report as usual

It doesn't allow you to group it on epic level but at least you got all worklogs in your report.

Best regards

Paul Alexander

Tempo product managers must have locked down their issue tracking since I too cannot get to their ticket (TT-81) any more.

Paul Alexander

I have not explored ScriptRunner yet - I probably ought to look into this now that it appears to be fully featured in the cloud offering. Thx for the reminder.

https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=cloud&tab=overview

David Vins

All of this feel just like it is, work arounds. It's frustrating that such glaringly obvious issues like this are not addressed, after years. Between stuff like this and constantly having to retrofit our process to the way these tools work (and don't work) we're now actively looking at other products, even outside of JIRA.

Paul Alexander

Having tried Christian's approach above using ScriptRunner, I can say that this does not solve the problem. My original, awful workaround is still better which provides the accurate hours report with work logs and I augment this with a separate report of the parent issues touched during the period.

David Vins

This is precisely why we're now actively searching for alternatives. Tired of the most basic functionality going unaddressed while having to search needlessly for addins that only half address the problem.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

tempo

tempo-timesheets