Issue Summary

The mapping issue starts when migrating pages to Cloud by using the Confluence Cloud Migration Assistant.

Basically, a page can contain Jira server URL. In some cases, we can find URLs with the following format:

${SERVER_HOST}/issues/?filter=${FILTER_ID}

Even after the link update, the entities ID is not getting mapped. As a result, each time that an end user click on the link, is getting redirected to a non existing page. 

Steps to Reproduce

1. Create a page that contains the following link: ${SERVER_HOST}/issues/?filter=${FILTER_ID}. Please replace the parameters according to your server environment.
2. Migrate the page by using the CCMA tooling
3. Apply the link fixing procedure link fixing procedure

Expected Results

• The ID should be mapped after or during the migration process. 

Actual Results

• Even if the URL is getting corrected, the ID will not be mapped again.

Workaround

A workaround could be to prevent the situation before migrating to Cloud. To do so, you will need to search for the occurrences in your own server and remove the URLs before moving to Cloud.

SELECT c.contentid, c.contenttype, c.title, s.spacekey, s.spacename,
'${SERVER_HOST}/wiki/spaces/'||s.spacekey||'/pages/'||c.contentid AS "URL"
FROM CONTENT c
JOIN BODYCONTENT bc
    ON c.contentid = bc.contentid
JOIN SPACES s
    ON c.spaceid = s.spaceid
WHERE c.prevver IS NULL
    AND c.contenttype IN ('PAGE', 'BLOGPOST')
    AND bc.body LIKE '%${SERVER_HOST}/issues/?filter=%'; 

The second option will require the Confluence Cloud REST API, search for the content on Cloud, parse it and then replace it.