Description

After migrating Confluence from DC to Cloud (via CCMA), some older blog posts are linked using a pages/viewpage.action?spaceKey pattern instead of the more common /spaces/<SPACE_KEY>/blog/... pattern.

For example:

https://<prod-confluence>/pages/viewpage.action?spaceKey=ENS&postingDay=2018%2F6%2F7&title=Increased+site+speed

• These URLs logically refer to blog posts that do exist in the destination cloud site. Still, the current Confluence link‑fixing tools (LMS / “Update product links”) don't recognise this pattern as a supported Confluence link type. They therefore can't update these URLs to the corresponding cloud blog URLs.
  As a result, after migration and link fixing, such links still point back to the old DC base URL and require manual correction.

Current Behavior

• Confluence link fixing supports a defined set of Confluence link types (page, blog, display, tiny URL, etc.) as documented in: Supported Atlassian apps and types of links
• The pages/viewpage.action?spaceKey=...&postingDay=...&title=... pattern is not among the currently supported link types.
• When link fixing runs with the correct DC base URLs configured, these viewpage.action?spaceKey links are not detected/mapped and remain unchanged.

Example from a migrated sandbox

Old DC URL:

https://<prod-confluence>/pages/viewpage.action?spaceKey=ENS&postingDay=2018%2F6%2F7&title=Increased+site+speed

Expected Cloud URL:

https://<cloud-site>.atlassian.net/wiki/spaces/ENS/blog/2018/06/07/<new_blog_id>/Increased+site+speed

The blog post exists in the cloud, but link fixing can't derive the mapping from this legacy URL format.

Suggested Solution

Extend the Confluence link‑fixing / LMS support to include the pages/viewpage.action?spaceKey=...&postingDay=...&title=...pattern when:

• The base URL matches a configured “Migrated from” DC Confluence URL, and
• The spaceKey + postingDay + title can be resolved (via migration metadata or content index) to a migrated blog post in the destination Cloud site.
  Specifically:
• Treat viewpage.action?spaceKey=...postingDay=...title=... as a Confluence blog link type,
• Resolve it to the correct /spaces/<SPACE_KEY>/blog/YYYY/MM/DD/<pageId>/<title> URL in Cloud, and
• Update the stored URL during link fixing accordingly.

Expected Outcome

• After link-fixing runs, links in legacy pages/viewpage.action?spaceKey format should be updated to the appropriate cloud blog URLs, consistent with other supported Confluence blog link patterns.
• Customers would no longer need to manually find and correct these URLs, reducing post‑migration cleanup work.

Why this matters

• Some customers have older or mixed URL patterns for blogs, especially when environments have been upgraded or reconfigured over time.
• These legacy blog URLs represent a “long tail” of broken links that remain even after normal link fixing has run and corrected more standard patterns.
• Supporting this pattern would improve the completeness and predictability of link fixing for Confluence migrations.

Workaround

• Currently, there is no known workaround for this behavior. A workaround will be added here when available.