Why does issue "key" not exist in tempo timelog API anymore?

Isabelle Bolt

Previously, I was able to use issue "key" as part of Tempo API

{

"self": "https://api.tempo.io/4/worklogs/3222",

"tempoWorklogId": 32222,

"issue": {

"self": "https://myurl.atlassian.net/rest/api/2/issue/22222",

"id": 29119

},

"timeSpentSeconds": 1800,

"billableSeconds": 1800,

"startDate": "2022-10-11",

"startTime": "17:00:00",

"description": "meeting",

"createdAt": "2022-10-14T16:01:40Z",

"updatedAt": "2022-10-14T16:01:40Z",

"author": {

"self": "https://url/user"

},

Now under issue, the key "key" does not exist anymore. Why has this been removed? It means now I will have to add an additional API call to my service, making this more inefficient. 

Fabio Racobaldo _Catworkx_

Hi @Isabelle Bolt ,

based on that documentation https://apidocs.tempo.io/#tag/Worklogs/operation/getWorklogs, that rest api will provide you issue id and not the key. 

You can raise a request to Tempo team through the following url https://tempo-io.atlassian.net/servicedesk/customer/portal/6/user/login?destination=portal%2F6

Hope this helps,

Fabio