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.

Choose which time records are exposed as standard Jira fields

Tempo reuses the standard Jira field timeSpent for Registered Time (R), while Billable Time (B) and Planned Time (P) are kept in internal fields. Tempo also reports the originalEstimate in some places, maybe also remainingEstimate.

Atlassian does not offer field-specific access permissions in Jira issues. That means if a customer has access to your Jira project, they can see worklogs, even if administrators hide them from issue screens. This causes confusion – to put it mildly – if the Tempo Billable Time used for invoices differs from the Registered Time exposed as time spent on the Jira issue.

Therefore I wish Tempo Timesheets would record the Registered Time in an internal field as well, so that us Tempo Admin users could choose which Tempo times to show for the Jira worklog, ideally per project.

I’m not convinced it has the same strong use case, but perhaps Tempo’s Planned Time and one of Jira‘s estimate fields could also be synchronized.

  • Christoph Päper
  • Jul 21 2023
Tempo Products Tempo Timesheets, Tempo Planner, Tempo Reports
Tempo Platform Cloud
  • Attach files