Why all issue links are broken when migrating cloud-to-cloud?

Question

We have tried to migrate a project from one of our cloud sites to another using the new migration tool for cloud migrations. Upon doing so, all our issue links were broken (i.e. sub-tasks, epics, etc.). This is a critical issue that we also raised with Atlassian, but have gotten no answer or support.

Dan Neduva · Answer

I just received the Bug/Issue ID for the fix: [MIG-1260] Sub-task and other items losing parent and link relation after a C2C - Create and track feature requests for Atlassian products.

You may follow its progress

Trudy P Claspill · Answer

Hello @Dan Neduva

Did Atlassian give you an issue ID for the bug? If so, could you please post it? I would like to watch that bug for updates.

Dan Neduva · Answer

Linkage between Epics/Story/Tasks/Sub-Tasks were broken, in all project types as far as I could see (JIRA Software). The initial migration from on-prem to cloud was fine and the links/parent IDs were intact, after migrating the site (cloud-to-cloud migration), the links broke/Parent IDs were gone.

After further investigation I found that when I created new tasks/subtasks inside the [Cloud] site, which was migrated from On-prem (JIRA Server), and then migrated them to another cloud site (using the cloud-to-cloud migration tool); the links stayed intact.

I also shared this information with Atlassian, so it gave them a clue into the issue, something that might have to do with how the links are formulated in the DB (Server vs. Cloud)