Introducing Release notes on Atlassian Community (Beta) – a new home for Cloud release notes

[Mykenna Cepek]

@Jess - Umm, that's not really a "survey". I seem to have to agree first to an "Atlassian Research Participant Agreement" which includes "audio, video, and screenshot recording". So, no.

I'm more than happy to provide some feedback, but please be more clear about your methods and the level of investment you are requesting of us.

[Michael Levinson]

First off, I wanted to share that the new method for publishing and sharing release notes is a definite step in the right direction. The improvements you've made are helping create better visibility into platform changes and direction, which is incredibly valuable.

I also wanted to offer some feedback and a potential enhancement that I believe would be extremely helpful—not just for my team, but for many organizations operating at scale within Jira.

The Challenge

One thing our organization has consistently struggled with is distributing and operationalizing release notes across a broad set of Jira administrators and product teams. While the content is valuable, translating release notes into actionable, trackable work within Jira still requires a significant amount of manual effort.

This becomes especially challenging when trying to ensure teams stay aligned on:

• What is Generally Available (GA)
• What is currently rolling out
• What is coming soon

Suggested Enhancement: “Out-of-the-Box Release Note Decomposition Agent”

It would be incredibly powerful if Atlassian provided an out-of-the-box agent capable of automatically decompiling release notes directly into Jira projects.

At a high level, the experience could look something like:

1. Project Selection

   • Prompt the user to enter a target Jira project key where release notes should be decompiled.

2. Epic Association

   • Prompt the user to either:
     • Provide an existing Epic Key, or
     • Type “create” to automatically generate a new Epic within that project

3. Automated Decomposition

   • Parse Atlassian release notes and create structured Jira issues
   • Preserve formatting, context, and relevant metadata
   • Tag items with release stage (GA, rolling out, coming soon)

Why This Matters

Providing a native, out-of-the-box capability like this would:

• Reduce manual effort required to operationalize release notes
• Improve consistency in how organizations interpret and track changes
• Enable admins and product teams to stay aligned on platform evolution
• Drive greater adoption of Atlassian’s roadmap and release transparency features

---

Thank you again for the continued improvements to the platform. I’d be happy to share additional context or examples if helpful.

[Jess]

@Mykenna Cepek , I'm so sorry that the participant agreement has that included and it's not clear that it's not required. For the survey, that is absolutely not required. It is a survey and release note comparison. I'll give feedback about the participant agreement.

[P_D_ Foerster]

Thank you for this really necessary upgrade to the current release notes provided by the blog!

Because my fellow community members already everything I thought of I can just agree and hope those points will be implemented until GA :)

Regarding "new this week" entries from the blog it would be great to have something similar, e.g. provide quick filter "Display recently added items only" with options:

• this week
• last week
• this month
• last month

Of course these filters are based on the created date which need to be available and visible for all users ;)

[Yatendra Chauhan]

Think abouts h it 😉 jg

[Darryl Lee]

@Michael Levinson regarding your idea for an “Out-of-the-Box Release Note Decomposition Agent”, at Team '26 in Anaheim, Atlassian had a session that walked users through creating an Agent that did something similar to what you're asking for:

AI for admins: Stay ahead on cloud releases 

In this hands-on lab, Atlassian admins will build a Rovo Agent to automate cloud release note reviews. You’ll pull weekly cloud release notes, classify changes as Action Required, Breaking, or Informational, and publish a clean Confluence summary – no copy/paste – then wire in Jira and Slack so critical updates become visible, trackable work. Walk away with a reusable pattern you can adapt across your own admin spaces.

I joked that if Atlassian wrote better Release Notes, we wouldn't need this Agent. (There is a bunch of details on telling it how to scrape the Cloud Change Blog, ugh!)

But yeah, here we are. :-D

Alas, the session was not recorded, but the shared Confluence page is still up:

• [Low Code] Changelog Charlie 

[Carsten Schäfer]

Hi all

yes, it seems a better way of publicly communicating changes and "type" is useful, too.

A few notes

1. Privide a way to see what comes in the next release cycle (for people like us that use monthly bundles) - we could then stop copying the release notes email into a confluence page every months
2. When copying the page link, the auto linker in Confluence fetches the wrong title
   1. https://community.atlassian.com/release-notes
   2. --> <title>Atlassian Community | Learn, connect, and grow</title>
   3. As the tab tirle is correct, I assume the title is overwritten by a script, but it is not resolved by the autolink in confluence.
3. I would like filter to show items that have a rollout schedulled, so we can plan for that change
4. We 'd love a RestAPI endpoint for this page that posasibly allows for richer filtering and more underlying info
5. As we cannot leaglly use Rovo, I would like to filter out features in any product that uses Rovo or requires AI

Happy to see that I can also easiyl select the table and export it to Excel, just in case.

Thanks

Carsten

[Wurm Peter]

If I want to check what has changed since my last visit, I do... what? I neither want to know what's completely new nor do I want to go through the entire list again and again. In it's current state it's pretty useless.

I should be able to follow a change and receive an email with every status-change. And "rolled out to your instance" is an important status-change.

I want a comment section on every change page.

BTW: "Annoucement" and "removed" are not "change type", they are status.