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.

API to match worklogs returned by Cost Tracker REST API to worklogs returned by Worklogs REST API

When getting worklogs made on a Cost Tracker Project via REST API (https://api.tempo.io/cost-tracker/1/projects/{projectId}/actuals/labor) the worklog has a "timeRecordId".
It is currently not possible to match this id to the Tempo worklog id that is returned by the "worklogs" REST API, making the mapping of the information returned very difficult.

It would be good to have an option to see which timeRecordId matches the tempoWorklogId.

  • Susanne Götz
  • Sep 28 2021
  • Shipped
Tempo Products Tempo Timesheets, Cost Tracker for Tempo Timesheets
Tempo Platform Cloud
  • Attach files
  • Katharina Puchstein commented
    February 02, 2022 10:02

    It would be helpful to not only have the Cost Tracker Worklog -> Timesheet Worklog Connection with the Timesheets ID in the Cost Tracker Response, but also the other direction: Given I fetched some Worklogs from the Tempo Timesheets Endpoint and want to get the Cost Tracker time records for them (if present).

    Maybe the Timesheets Endpoint /worklogs could return the ID of the Cost Tracker Worklog too if one exists and Cost Tracker is even installed.


    If this is not possible, maybe the Cost Tracker API could have something like a /labor endpoint that takes a list of (Timesheets) Worklog IDs as query param and returns the matching Cost Tracker time records if there are any.