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.

Adding Issue-level fields to GET /worklogs

As an integrator of Tempo Timesheets with other products such as Salesforce, I want to be able to call the GET /worklogs endpoint and have both custom and Tempo fields I associated with the Jira Issue be retrieved.

For example, I have the Tempo Account linked to Jira Issues (as opposed to a Work Attribute). Both the Name and Id of the Account should be in the JSON I retrieve.

Additionally, if I select certain Jira Issue custom fields to be included in the Tempo database, I would expect those to be included in the JSON for GET /worklogs as well. For example, I might have a field called "Milestone" on the Jira Issue. I go into Tempo Settings -> Custom Fields and check the "Milestone" field.

Being able to retrieve this information without extra API calls results in a more performant solution as well as reduces code complexity to retrieve data.

  • Nate Stuyvesant
  • Sep 17 2020
Tempo Platform Cloud
Tempo Products Tempo Timesheets
  • Attach files