Keep your weekly change check: move the Atlassian runbook before Sept 30

You open the same change page on the same day, scan the entries, and mark the ones that touch the tools your team depends on. Atlassian's Atlassian Cloud release notes page will stop being updated after September 30, 2026. The habit is small, but it catches the surprise before it becomes a support ticket, a broken automation, or a meeting where someone asks why nobody knew.

A small team does not have a dedicated platform admin. The ops lead is usually the person who notices when a change breaks a workflow, a report, or an automation. The weekly check is where that notice happens on purpose, not after a customer complains. It also gives the founder a short list of things to know, not a long list of vendor announcements.

Move the source before the ritual stalls

Atlassian's beta release-notes hub on Community is designed to become, over time, the main source for Jira, Confluence, and other cloud app changes, superseding the Atlassian Cloud blog. Atlassian's community release-notes hub updates in real time as changes ship, while the old Atlassian Cloud blog updated on a weekly cadence. A change can land between checks, and you can point the team to the exact note instead of a broad summary.

The failure mode is a broken link in the runbook, not a missed change. When the source moves, the ritual still runs, but it runs on stale information.

Make the switch in one sitting

Each step can be tested quickly. Do them in order, because each one depends on the previous one.

• Bookmark the hub called What's new across Atlassian, where Atlassian is moving its cloud release notes.
• Run one test pass with the New this week filter, which Atlassian added to Release notes on Atlassian Community to show release notes published in the last 7 days.
• Swap the old blog link in the runbook and weekly agenda before that date.

If time is short, do the swap first: the bookmark is easy to recreate, the pass can be redone, and the runbook is where the next person will look.

Keep the runbook scannable

Run the pass before you change the runbook. Open the hub, apply the filter, and read only the entries that could affect your team. Ignore the rest. This confirms the source works, not that you have read everything.

Look for entries that mention a field, a permission, a report, an integration, or a workflow your team depends on. If an entry is vague, open it and check whether it touches a page you maintain. If it does, write a short note in the runbook. If it does not, mark it as reviewed and move on. The pass should end with a short list of notes to review.

Use the unread indicators, added by Atlassian to Release notes on Atlassian Community, to mark newer release notes a user has not opened. Clear them in the same pass, or note why you are leaving them. Use the Release tracks changes view, added by Atlassian, to see release notes tied to upcoming Preview and Bundled releases. Use it to separate what is already live from what is coming, so the runbook does not fill with speculation.

Keep the runbook entry short. A date, a short summary, and the link are enough. If the change affects a workflow, add the owner and the next action. If it does not, leave it as a reviewed note.

Put the new link in the agenda before the next check. The agenda should name the source, the filter, and the person who will review the notes. If the check is a meeting, keep it short. If it is a solo pass, write the output where the team can see it. The ritual survives when the next person can pick it up without asking you.