Tempo Ideas

We cannot accurately aggregate time in a cross-project setup involving parent/child issue relationships.

Here’s our scenario:

• We have a main Jira project with a standard parent/child issue structure.

• In other Jira projects, teams are also working on related issues that follow their own parent/child hierarchy.

• The challenge is that the top-level parent in those other projects is actually a child issue in the main project.

As a result, we're struggling to generate reports in Tempo that accurately roll up time from all related issues (across multiple projects) to the ultimate parent issue in the main project.

Question:
Would be ideal if tempo timesheets could handle time aggregation across this kind of multi-project, nested hierarchy.