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

[Dan Neduva]

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]

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 

[Dan Neduva]

Yes, Atlassian support is on it now, we were in touch with one of their migration engineers/representatives. It is now under investigation by their Engineering department, who are currently looking into fixing this issue. We hope for a fix soon for release. Since this feature is currently in Beta, things like this are expected. I did want to make sure that it was written somewhere in the community for others to follow.

[Trudy Claspill]

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.

[Trudy Claspill]

Hello @Dan Neduva 

Welcome to the community.

Please note I am just another user, not a member of the Atlassian Team.

When did you raise the issue to Atlassian Support? Did you open a support ticket? Did you categorize it as a Migration problem? Did you open a Migration ticket with Atlassian Support prior to starting the migration to get support engaged in advance of your migration?

Are you saying the generic links between issues are broken, or child issues no longer show under Epics, or subtasks no longer show under their parent issue?

Did you migrate Team Managed or Company Managed projects? Software, Service, or Business/Work Management projects?

Can you provide more details on exactly what you mean by the links being broken?

[Dan Neduva]

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)