Symptoms

When you transfer a Jira Issue from one Project to another within the same cloud instance, the corresponding link on the Confluence cloud gets redirected automatically when we access them. However, when you migrate content from one cloud instance to another, redirection does not occur. Instead, all the links of the moved issue become broken on destination confluence

Analysis

• When we move an issue from one project to another, it will be recorded in the following tables
  • changeitem
  • moved_issue_key

• When using Source Confluence, accessing the former issue key will automatically redirect to the destination. This is facilitated by the records present in the Jira Database and the existence of application links.

• However, if we migrate both Jira and Confluence to a new cloud instance, it may result in issues. This is because the historical data from these tables corresponds to the moved issues that are not getting migrated

Suggestion

It would be better to migrate all changeitem & moved_issue_key table data to the cloud which will avoid this situation. Please reach out to Atlassian Support if you observe similar symptoms