Issue Summary

Link Fixing Tool blindly replaces base URLs on Jira Server/DC paths containing /secure (e.g., user profiles, RapidBoard/agile boards, Structure boards, and admin screens) without verifying target entity mapping or valid Cloud endpoints, resulting in broken or malformed Cloud links marked as SUCCESS.

Steps to Reproduce

1. Migrate Jira Server / Data Center projects to Jira Cloud using the Jira Cloud Migration Assistant (JCMA), where issue descriptions, comments, or custom fields contain links pointing to Server /secure/ endpoints (such as /secure/ViewProfile.jspa, /secure/RapidBoard.jspa, /secure/StructureBoard.jspa, or /secure/admin/).

1. Run the Link Fixing Tool on the destination Cloud site to update migrated links from the source base URL to the destination Cloud base URL.

1. Review the Link Fixing audit report/CSV export and inspect the updated links on Jira Cloud.

Expected Results

The Link Fixing Tool should validate entity existence and map URLs to their valid Cloud counterparts, or skip replacement if an equivalent entity/endpoint does not exist:

• User Profiles (/secure/ViewProfile.jspa?name=<username>): Should be remapped to the user's Cloud Atlassian Account profile (e.g., https://<site>.atlassian.net/jira/people/<accountId>), or skipped if the user is unmapped/inactive.

• Agile Boards (/secure/RapidBoard.jspa?rapidView=<id>): Should verify that the rapidView ID is mapped to a valid Cloud board before replacement, rather than leaving obsolete paths or unverified query parameters.

• Third-Party Apps (e.g., Structure: /secure/StructureBoard.jspa): Should not blindly replace base URLs for Server plugin-specific paths that do not exist or function on Cloud.

• Administrative Paths (/secure/admin/*): Should not be rewritten to Cloud base URLs, as DC internal admin paths, draft workflows, and token parameters do not map directly to Cloud admin screens.

• Links without valid Cloud entity mappings should be reported as SKIPPED with an appropriate reason.

Actual Results

The Link Fixing Tool performs a blind string replacement of the source base URL with the Cloud base URL for paths containing /secure/*.

The tool flags these operations as SUCCESS in the audit logs, even though the resulting URLs point to non-existent endpoints, invalid parameters (e.g., DC usernames instead of Account IDs, DC plugin paths), or produce HTTP 404 / malformed pages when accessed in Cloud.

Workaround

Contact Atlassian Support for the same