Issue Summary

After a Confluence DC→Cloud migration, running Confluence link fixing (LMS / “Update product links”) leaves some standard blog links still pointing to the server/DC base URL, even though:

• The source blog existed in the original DC space, and
• The target blog exists in the destination Cloud space, and
• The URL pattern matches a supported Confluence blog link type.

The Confluence link‑fixing job completes successfully overall and updates many links, but these specific blog URLs remain unchanged.

Steps to Reproduce

1. Migrate one or more Confluence spaces with blogs from DC to Cloud using CCMA.
2. In Cloud, locate a page that contains a Confluence blog link in the form:

   • https://<confluence-dc-base>/spaces/<SPACE_KEY>/blog/YYYY/MM/DD/<old_blog_id>/<title>

   • where the corresponding blog has been migrated and is accessible in Cloud under the same space key.
3. In the Cloud admin UI, run Update product links (Confluence) with:
   • Product: Confluence
   • Destination URL: https://<cloud-site>.atlassian.net
   • Migrated from: <confluence-staging-dc-base>
   • Migrated from a staging instance (Production): <confluence-prod-dc-base>
4. Wait for the Confluence link‑fixing job to complete. The job result typically shows:
   • Status: COMPLETE
   • CONFLUENCE_LINK with a large updatedCount and some skippedCount, no job‑level failures.
5. Reload the affected Cloud page and inspect the blog link.

Expected Results

The Confluence link‑fixing job should rewrite the DC blog URL:

https://<confluence-dc-base>/spaces/<SPACE_KEY>/blog/YYYY/MM/DD/<old_blog_id>/<title>

to the corresponding Cloud blog URL:

https://<cloud-site>.atlassian.net/wiki/spaces/<SPACE_KEY>/blog/YYYY/MM/DD/<new_blog_id>/<title>

The link on the Cloud page should point to the migrated blog post in the correct space.

Actual Results

• The link‑fixing job completes successfully and updates many other links, but:
• The blog link on the page still points to the DC URL using the /spaces/<SPACE_KEY>/blog/.../<old_blog_id>/... pattern.
• The destination Cloud blog exists and is accessible, but the URL was not rewritten.

Workaround

• Manually edit affected Confluence pages and update the URLs to the correct Cloud blog URLs.
• This is not practical at scale for larger spaces.