Issue Summary

When Jira and Confluence are migrated from Data Center to Cloud into two separate Atlassian Organizations / Cloud sites, the Product Link Fixing (LMS) tooling cannot establish cross-organizational mappings. As a result, links embedded in Jira work item descriptions/comments referencing migrated Confluence Data Center pages remain broken and point to the legacy Data Center base URL.

Steps to Reproduce

1. Migrate Jira Data Center to Cloud site A (e.g., https://site-a.atlassian.net) within Organization A.
2. At a separate time, migrate Confluence Data Center to Cloud site B (e.g., https://site-b.atlassian.net/wiki) within Organization B.
3. Observe that Jira issues contain descriptions/comments with URLs pointing to the legacy Confluence Data Center base URL.
4. Attempt to run Product Link Fixing / LMS to update legacy Confluence links in Jira Cloud site A to point to their new Cloud URLs in Confluence Cloud site B.

Expected Results

The link fixing tooling can resolve and rewrite legacy Data Center links to their corresponding Cloud destinations across different Cloud sites/organizations, or allow admins to supply cross-site mapping metadata.

Actual Results

Product Link Fixing (LMS) is only supported within the same Cloud site / organization boundary. The jobs cannot map or detect the destination pages in the separate organization, leaving legacy links untouched and broken.

Workaround

Customers can use API or contact Atlassian Support and ask them to run link fixing for them. MSEs should use the steps mentioned in the release readiness guide for cross-site link fixing.