Symptom
After a Data Center to Cloud migration, the Worklogs tab of a Jira issue shows worklogs, but the Jira REST API returns none for that issue. The Tempo data for the issue is much larger than the Jira data.
Cause
The site was migrated more than once with the Jira Cloud Migration Assistant (JCMA). Between migrations, Atlassian changed the issue mapping, so a Cloud issue ID pointed to a different issue. The Tempo data from the first migration was not removed, so the issue now holds worklogs from two different issues. Deleting projects or resetting the Jira Cloud site before a new migration leads to the same stale data.
Resolution
Contact Tempo Support. Tempo can correct the data for the affected site.
Prevention
-
Do not run repeated JCMA migrations against a production site.
-
If a new migration is required, contact Tempo Support first. Support can decommission the Tempo apps and reinstall them on Jira Cloud. Then run the new migration.
Source: Tempo Support and Engineering.