Issue Summary

After running LMS (Link Migration Service) for a Server to Cloud (S2C) migration, Jira links using the /secure/ path pattern found in Jira issue descriptions, comments, environment fields, and text custom fields are not 100% updated to the destination Cloud URL.

Affected URL pattern:

https://<source-jira-base>/secure/<anything>

Examples include:

https://agile.corp.edp.pt/secure/RapidBoard.jspa?...
https://agile.corp.edp.pt/secure/Dashboard.jspa?...
https://agile.corp.edp.pt/secure/CreateIssue.jspa?...

Confirmed customer impact: Thousands of unfixed /secure/ links across a single tenant after multiple LMS runs.

Note: This does not cover /secure/attachment/ links which are a separate category

Steps to Reproduce

1. Perform a Server to Cloud (S2C) migration of a Jira instance where issue descriptions, comments, environment fields, or text custom fields contain links in the format https://<source-jira-base>/secure/<path>
2. Run LMS link fixing (via AdminHub or direct API) against the migrated tenant
3. After LMS completes, check Jira issue descriptions/comments for links still pointing to the source base URL with the /secure/ path

Expected Results

All (or most) /secure/ Jira links in issue content are rewritten from the source base URL to the destination Cloud URL after LMS runs.

Actual Results

Thousands of /secure/ links remain pointing to the source Jira Server URL after LMS execution. The domain is not swapped and the links remain broken for end users.

Workaround

Currently there is no known workaround for this behavior. Contact support for options