Skip to main content

3 posts tagged with "confluence-admin"

View All Tags

Fix Broken Links After a Confluence Cloud Migration

· 7 min read
NGPilot
Quick Answer

A Cloud migration moves your content. It does not fix the links inside it. Anything a user typed by hand — an old Jira URL in a page body, a Server link pasted into a comment in 2021, a macro pointing at your old domain — survives the migration verbatim and now points at a host that no longer exists. Find them with advanced search on the old domain, define one mapping rule per domain, preview every match before rewriting, and sweep page bodies, blog posts, comments, macro parameters and attachment names separately.

The migration is done. Pages moved, spaces are there, the site is live and people are using it. Then someone clicks a link in an onboarding page and lands on a 404 that points at jira.mycompany.com — a hostname that stopped answering the day you cut over.

It is a common post-migration complaint, and it has a specific cause worth understanding, because the fix is different depending on where the link is.

What you'll learn
  1. Which links the migration fixes and which it silently leaves behind
  2. Why comments and macro parameters are where the damage hides
  3. The search queries that actually find the stragglers
  4. How to build mapping rules that are safe to run in bulk
  5. Why Jira links inside Confluence need their own mapping

Find Stale Pages in Confluence (All Plans)

· 10 min read
NGPilot
Quick Answer

On Premium and Enterprise, open Space settings → Content manager and use the Last active dropdown — it shows pages not viewed, updated or commented on, with options from 7 days to 6 months back. On Free and Standard that screen does not exist, so use CQL instead: type = page AND lastModified < now("-365d") ORDER BY lastModified ASC. Neither route is complete: Atlassian documents that Last active excludes pages with children, and blogs sit outside the tool entirely.

A Confluence instance does not rot all at once. It accumulates. A project wraps up and its space stays. A team splits and both halves keep the old runbook. Someone copies a page instead of linking to it, and now two versions exist with different numbers in them. Five years later a new hire searches for the onboarding doc, lands on the 2021 version, and trusts it.

The cleanup instinct is right. The problem is that "find stale pages" is one of those tasks where the answer depends entirely on which Confluence plan you happen to be on, and almost nobody knows that until they go looking. Here is what each tier actually gives you, in the order you should try it.

What you'll learn
  1. The native way, and the four documented omissions
  2. Why Atlassian deliberately skips your most-outdated pages
  3. The CQL query that works on every plan, including Free
  4. Why "not edited" and "nobody reads it" are two different lists
  5. What to do with the list once you have it