Tempo migration v3 to v4 related question

[Remie Malik]

Hi all,

We are working at the moment with version 3 Tempo API. Since the recent reports it states that next month version 3 will end and version 4 will be used.

Before we called:

https://api.tempo.io/core/3/worklogs/issue/{issue_key}?fields=summary

And now will be

https://api.tempo.io/4/worklogs/issue/{issue_id}

However, we do not have access to the new issue_id. How can we work around this issue?

If we only know the issue_key from the software and we gather worklogs from Tempo from our employees.

Kind regards,

Remie

[Kevin Giesübel]

You have to make an additional request to the jira rest api, check this: https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-get

Make a request to /rest/api/2/issue/{issueIdOrKey} with your issue key and in the response you get the ticket data including the issue id.

Best regards,

Kevin