Atlassian's weekly cloud changes page stops on 30 September. Here is what replaces it.

[#1]

If you are an admin, you almost certainly have a habit built on the Atlassian Cloud changes page at confluence.atlassian.com: a Monday bookmark, an RSS feed, a copy-paste into a change-advisory note. That page carries a banner saying it will no longer be updated after 30 September 2026 (this week's edition). The banner has been there since May, which is exactly why most of us have stopped reading it. Here is where the notes go, what the new surface does that the old one never could, and the two things it cannot do yet. 📡

Where it moves

Release notes on Atlassian Community at community.atlassian.com/release-notes, announced as a public beta on 18 May (the announcement). Same content as the weekly page, updated continuously rather than in a Monday batch.

What it does that the old page could not

Read live this morning:

1. Status per change, not per week: Planned, Rolling Out, Generally Available, and Rolled Back, with a Rollout schedule column ("Starting in June 2026", "No timeframe yet"). The old page could only say "rolling out" and leave you to check your site, and it never told you when a change was reversed. Rolled Back on its own justifies the move for anyone who writes change notices.
2. Filters for App, Status, Change type, and a New this week toggle, so a JSM-only admin sees JSM-only changes.
3. Impact rating, Low, Medium or High, so you can filter to High and read a handful of items instead of thirty. Atlassian labels it AI-generated and in beta, and asks for feedback on its accuracy, so treat it as a first pass, not a verdict; a Low-rated change to email notifications can still be a High for a service desk.
4. A separate Release tracks changes tab. If you are on Enterprise and run release tracks, this is the view that tells you what your next track bundle contains. It has never had a page of its own before.

Filtering to Jira Service Management and High impact this morning returned nine items: seven still Planned or Rolling Out (including the field schemes migration that has been rolling since June), one Generally Available since July, and one Rolled Back, a feature-flag removal that the old page would have listed once and never revisited.

What it cannot do yet, verified by looking for it

There is no subscribe, RSS, email or watch control on the page. A commenter on the May announcement asked for exactly this (watch an item, be told when its status changes) and it is not there today. So the one thing the old page gave you for free, a feed you could pipe into a channel, is missing at the moment the old page ends.

The workaround until it exists: the filter state is carried in the URL. Filter to your apps and High impact once, copy the address bar (it looks like https://community.atlassian.com/release-notes?products=JIRA_SERVICE_MANAGEMENT&impactRatings=HIGH), and pin that link in your admin channel; every open of it is a fresh, filtered read with no clicking. Pair it with a weekly ten-minute slot for whoever owns change communication. That is not a feed, and I would rather say so than pretend one exists; if you want the feed, the comments on the May announcement are where Atlassian said it is listening.

Two things to know before you switch

1. The new home is the Community, and the Community migrates to a new platform on 22 September. That is eight days before the old page stops. Nothing says the release-notes page will break, but bookmark it again on 23 September and confirm the URL and filters survived before you delete the old one.
2. Deprecations still live somewhere else. The developer changelogs for Jira and Confluence carry API and app deprecations with dates that the release notes only summarise. If your estate has integrations or Marketplace apps, keep the changelog as your second source; the release notes are the admin view, the changelog is the contract.

The three-source radar I would run from October

1. Release notes on Community, filtered to your apps, weekly, from the pinned URL.
2. The developer changelogs, monthly, for anything with a deprecation date.
3. The product boards on the Community, because Atlassian Team members post the human version of a change there before the docs catch up, and the comments are where the rollout problems surface first.

All links verified live on 7 September 2026. The page is in beta and will change, check it before you rely on a detail here.