Best practise for migrating issue links when partially migrating from Jira Server to Cloud?

Question

Hi,

my company is patially migrating our Jira from Server to Cloud and we now ran into the problem, that on cloud side all issue-links are missing and on server side all issue-links are still pointing towards the server issue instead of the migrated cloud issue.

Are there any best practises to get the links correctly migrated?

I successfully linked our Jira Server to our Jira Cloud, so I can link any cloud issue to server issue.

Best Regards,
Roland Siegel

Michele De Pascalis · Answer

Hi Roland, sorry to reopen this topic after so long: did you eventually find a solution for this?

Roland Siegel · Answer

I just tested which data gets migrated.

Atlassians statement is correct. All links to projects/issues which are not migrated will not be persent in cloud. But when you afterwards migrate these projects the links will be corretctly generated between cloud issues.

So I have to figure out a workaround for linking between cloud and server.

Roland Siegel · Answer

Hi Seba,

ah, I understand, thanks a lot for this information. :)

I did now update the appliction links but all he did was updating links inside of text fields like description and comments. The direct links between issues pointing towards not migrated projects are still missing.
Maybe there were not migrated?

I found this:

https://support.atlassian.com/migration/docs/troubleshoot-migration-with-jira-cloud-migration-assistant/

Links to projects and issues that aren’t included in the migration
If you have chosen to migrate in smaller batches, links to projects or issues that haven't yet been migrated will be missing until that linked item is migrated.

How does this fit in with your statement, that links to server projects will be kept when Atlassian tells that the links will not be migrated?

Best Regards,
Roland