Tempo Ideas

Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.

More detailed fallback logic for determining someones team role in the Account report API

When running a report by Account, or calling the rest/tempo-timesheets/3/report/account/[account num]/timeandexpenses REST API, we have found that people's team role and rate can be incorrectly returned in the following conditions. We would like to see a more detailed fallback logic in the API or a message indicating an issue.

If you have billable time against an account in a project,
and you are a member of multiple tempo teams (with different roles, usually on different projects),
and you don’t have a Team specified on the Jira issue, it will return a randomly selected team and role of yours which may not be correct for this project even though there is only one Team linked to the project.

Instead, it should either:
Try and use a team linked to the project, or there are multiple teams then the one that you are a member of; or
return the team as "unknown" or "unspecified" or something showing that there is an issue instead of assuming it is OK.

It should be less likely that you are a member of multiple teams linked to a project and that should give a more accurate assumption of your team role and rate than what happens now, but I do acknowledge that is possibly quite a complex bit of SQL/JQL.

  • Damian Wheeler
  • Dec 9 2025
Tempo Products Tempo Reports, Tempo Timesheets
Tempo Platform On-Premise
  • Attach files