Getting Not Found for "tempo-timesheets" api after credentials changed

[Rupa Mistry]

Hi Team,

I have been using the following url "https://******/rest/tempo-timesheets/3/worklogs?projectKey=DER&dateFrom=2018-06-11"  for fetching the issues for particular project key.

But few days ago we changed the credentials that we were using for fetching the api, and from that day the api is not working, we are getting "Not found" message for all the project, can you please guide on how should we proceed to resolve this issue.

[Ignacio Pulgar]

If it is a Jira Cloud instance, it may have something to do with this:

https://confluence.atlassian.com/cloud/blog/2018/06/say-goodbye-to-usernames-in-atlassian-cloud

So, you may change the authentication method from basic to anything else (I think Oauth is the most recommended way).

[Rupa Mistry]

No, I am asking about accessing the data that is returned by this api, why the data is not available now ?, Do I need to make certain changes in profile settings so that jira can return the data through api, for my account ?

[Somo Sharma]

Hi Ignacio,

I think the link is correct, can you tell me how should I proceed to change the authentication process to access the timesheet api data.

[Susanne Götz _Tempo_]

Hi Rupa,

We did our best to reach out to as many people as we could to give advance notice of action required for APIs, but some of our customers may not have received the message.

Please take a look at https://tempo-io.atlassian.net/wiki/spaces/TEMPO/pages/165249146/2018-05-01+Action+required+for+APIs for details about the action required

Regards,
Susanne Götz
Tempo team