This bug is for Cloud to Cloud. See the related bug for Server to Cloud.

Issue Summary

Is this reproducible: Yes

Steps to Reproduce

1. Create an application link between source cloud and destination cloud instance. 
2. Create links between issues on source Jira cloud and destination Jira cloud. 
3. Do a migration of the projects containing the links. 
4. Post migration the link on the source cloud issue will still be pointing to the destination cloud URL. But throwing an error. 
5. The URL will be correct but the link will throw an error in the GUI. 

Expected Results

Convert remote links into local links.

Actual Results

The link points to the correct URL but an error is seen as "Failed to load remote issue because remote site is not linked"

Workaround

The only workaround is to delete the link and re-create it manually. The issue is caused because the links are stored in "RemoteLink" table when there are links between Jira cloud and other Jira cloud instances. But when both source and destination are in cloud the links are stored in a different DB table "IssueLink" + "IssueLinkType" , and currently no conversion happens between these 2 different types of links during migration. 

A manual re-creation of the link creates the link locally. Though this workaround could be difficult to scale for large number of remote links. 

Relevant REST API documentation:

• Delete remote issue link by ID
• Create issue link

If you need further assistance on this scenario, please reach out to Atlassian Support.