Summary

Given a hybrid migration scenario, where Confluence was migrated from DC2C, and Jira will stay in DC, remotelinks in Jira DC issues (confluence mentioned) should automatically be updated to reflect the Confluence Cloud new URLs and IDs.

During the space's import phase, Confluence Cloud should send a request to DC to refresh/update the remote links in Jira DC.

Workaround

There are two workarounds

(1) Not scalable

1. Copy the page in Confluence Cloud, where the Jira issue is mentioned.
2. Publish the copied page (at this time, a new remotelink is created in Jira DC).
3. Delete the original page (at this time, the old/wrong remote link is deleted from Jira DC).

(2) Scalable

Execute an internal Atlassian script to generate update SQL statements to be executed in Jira DC database.