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

[Roland Siegel]

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

[Sebastian Krzewiński]

Hi @Roland Siegel 

I got the same issue like you. To fix that you need to request to Atlassian for issue link fixing. See https://confluence.atlassian.com/confkb/after-a-successful-server-to-cloud-migration-url-links-are-broken-in-the-new-cloud-instance-1077781093.html

Regards,

Seba

[Roland Siegel]

Hi Sebastian,

and thanks for your hint, but this doesn't help me in our case.

We do a partial migration. That means in step 1 only six from all our jira projects will migrate to cloud and now I need all links from all issues on the cloud side pointing to the server issues which did not move.

And I need all links from server issues pointing towards the cloud issues which did move.

And in fact we actually are missing any links in our issues on cloud side. They are not "broken" an pointing towards server (this would be great in our case), but they are simply not there.

The link above only helps when all projects move to cloud at once.

Best Regards

[Sebastian Krzewiński]

Hi Roland

We are also in next phase of partial migration from server to cloud so links between both instances are important.

At the beginning I thought exactly like you, so I ask atlassian about that. They told me that this tool will check what projects was migrated and fix links only for those projects in Cloud. Tool will leave links to server instance if it point to not migrated projects.

From server side we decide to not modify links on db or recreate them but create redirection on proxy side.

Regards,

Seba

[Roland Siegel]

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

[Roland Siegel]

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.

[Michele De Pascalis]

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