Please continue the Jira Issue Key information as before or allow the ability to expose the Tempo Account information as part of the Retrieve Worklogs API.
We are using the Tempo REST APIs to replicate our Tempo Worklogs into our SAP system to create the billing documents for our clients.
The worklog API of Tempo does not include the Tempo Account Information of the worklog, so we need to retrieve the Jira Issues for all Worklogs that replicate and get the Tempo Account Information from there.
In REST API v3 you returned the Jira Issue Key and we could query the Jira REST API via JQL to retrieve multiple Issues at once to look up the Account Information.
In v4 you return only the issue Id. The Jira REST API can't search for issue Id's, which means we have to look up each Jira Issue that is referenced in the exported Worklogs one by one - this leads to 100s of queries against the Jira REST API.
Mirushe Redzepovska
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |
We are also running into the same issue, whereby we need to make 100s of individual requests to JIRA to retrieve the specific ticket / issue information.
Adding the
issue.keyto v4, will resolve this issue for us to.Voted +1
See also https://ideas.tempo.io/ideas/T-I-518