Worklogs logged after migration to cloud not visible through API but hours logged before are

[Bart Jansen]

We are using the rest API for getting all worklogs. This used to work fine on the server.
We have migrated to the cloud. Now all worklogs from before the migration are visible through the API that is connected to the Cloud. But work logged after the migration doesn't show thought the API.

We do use the tempo timesheets add-on. But as I understand the worklogs are still located in the Jira database.
Any ideas on how this could be possible?

[Susan Wu · Accepted solution]

Hi @Bart Jansen ,

Unlike worklogs on the Server, you will need to use Tempo REST API to get Tempo data on Cloud. Please refer to these articles to find more details:
1. https://tempo-io.atlassian.net/wiki/spaces/KB/pages/488931333/Why+do+the+Jira+worklogs+appear+with+the+author+Tempo+Timesheets+instead+of+the+user+s+name

2. https://tempo-io.atlassian.net/wiki/spaces/KB/pages/2954788869/Tempo+and+Jira+worklog+sync+on+Cloud

3. https://tempo-io.atlassian.net/wiki/spaces/KB/pages/1854931177/Tempo+data+storage+on+Cloud

You can also check out these Post-Migration KB's to understand the differences between Server and Cloud to adjust your workflows. https://tempo-io.atlassian.net/wiki/spaces/KB/pages/3117973599/Post+Migration+Product+Onboarding

Hope this helps.

Best Regards,

Susan Wu

Tempo Product Expert

[Bart Jansen]

Thanks Susan, after some further looking into it I found the reason why data looked incomplete. Since we are working in Jira and Tempo Cloud the worklogauthor is no longer the user in Jira but the everything is being logged through the user "Jira Service User". 
So now I have to also connect to the Tempo API and retrieve the actual ID of the user.