Alex Chiu Atlassian Team

Hi @Richard Scholtes Scale and consistency are two of the main reasons we’re using AI here. It can bring together a lot of different sources of information to provide a consistent Impact Rating across a large volume of changes. That said, the current rating doesn’t use an individual customer’s organizational data, so it…

Hi @Julia Foden Impact Ratings were being released gradually when you posted this, but they should now be available to everyone. Please let me know if you still don’t see them. On why we use AI: the assessment doesn’t replace the judgment of the team responsible for the change. Their internal assessment is a key input,…

Hi @Charlie Misonne Completely agree that transparency is critical, we plan to keep the AI label and verification guidance visible. To clarify how it works behind the scenes: the AI assessment doesn’t operate in a silo or override feature teams. In fact, the team delivering the change provides the foundational assessment,…

Hi @Jeffery Candiloro That’s a fair question. The AI assessment doesn’t replace the judgment of the feature team responsible for the change. In fact, the team’s internal assessment is a key input into the Impact Rating. AI helps us turn that information into a consistent classification across a large volume of release…

Hi @Jamie Knight The impact ratings were in the middle of a gradual rollout when you posted, but they should now be live for everyone. If you’re still not seeing them on your end, please let me know. Regarding subscriptions: thank you for highlighting this! We know how important it is to easily stay on top of new release…

Hi @Darryl Lee Excellent timing then! You're right that there's a lot of data we haven't been surfacing yet — Release Tracks support is one we've been wanting to ship ASAP. The goal is exactly what you said: an official, reliable place for track-specific notes so folks don't have to reverse-engineer it from APIs or…

Hi @Wurm Peter Great question — we publish these updates ahead of full availability because we do a randomized, phased rollout. This means some customers will see the new changes before others as we gradually expand access. We share the announcement early so everyone knows what's coming and can plan accordingly, rather…

Hi @Bill Sheboy Some Atlassian changes take longer to roll out than others — this largely depends on each feature development team's rollout plan. That said, you're correct that some of these need to be cleaned up on our end. My team is working closely with feature development teams now and going forward to improve the…

Hi @Antal Vig _ Communardo This page is updated in real time. As Atlassian feature development teams publish new release notes, they appear here immediately — no more waiting until next week for the weekly blog post to see what's changed.

Hi @Mykenna Cepek First off, your screen-scraping setup for the old blog is genuinely impressive — but it's also exactly the kind of pain point that motivated the team to build this. Really glad the filtering, rollback visibility, and text search are landing well. These were built on the back of helpful customer feedback…

Hi @Josh Thank you for calling out the parameterized URLs — that's one of the details the team wanted to nail down, so it's great to hear it's landing well. One improvement we've already prioritized is a time-based unread indicator that lets admins quickly filter to only show unread release notes posted within the last…

Hi @Josh Thank you so much for the kind words and encouragement — it truly means a lot to the team working on this. We still have a lot of exciting improvements to change management in the pipeline, so stay tuned — and I want to again thank everyone here for being such supportive voices on Atlassian Community!

Hi @Dirk Ronsmans Thank you for sharing this — really happy to hear the this new feature is working well for you and helping you discover features you weren't even aware were in the works! That's exactly the kind of outcome we were hoping for! Your feedback echoes what we've heard from others — it's not immediately clear…

Hi @Julia Foden Unfortunately for that specific change, I don't believe a separate Community post was made — otherwise, that would normally be the best way to provide feedback directly to the product team building that feature. One of the future improvements we'll be making is bringing release notes closer to additional…

Hi @Darryl Lee Thank you so much for the kind words, our team really appreciate it! And thank you for maintaining the Public Release tracks release notes page for so long. The Atlassian Community is great because of contributors like you who go above and beyond to help others stay informed. I am happy to share that a…

Hi @Bill Sheboy Thanks for your feedback and for taking the time to share your observations! To clarify a couple of points about how the new Release Notes on Atlassian Community works — the release notes here actually function more like a live news feed rather than a periodic publication. They're consistently updated in…

Hi @__ Jimi Wikman Thank you for your detailed comment and the additional context — this is extremely helpful, and I'll be sure to share this more broadly internally with our partner teams in Jira and other product teams. As mentioned in the post, we know that for customers with more complex requirements, 30 days is often…

Hi @Mathew Lederman If your organization is using Release tracks, the Jira Bundles tab in App updates at admin.atlassian.com is the best place to preview which changes are included in the seasonal bundles before they are released. I completely understand your concern about having to check multiple places to stay on top of…

Hi @Carolyn White & @Mathew Lederman Thank you both for sharing your feedback on the timing of the final seasonal release of the year — that’s really helpful context. I’ll make sure to pass this along to our partners in the Jira team.

Hi @Josh Thanks for your feedback — I definitely understand that these changes will introduce some additional operational complexity. As mentioned in the original announcement blog, our broader ambition is to scale this model beyond Jira. The goal is to first prove the customer benefits of the seasonal release approach…

Hi @Stephen_Lugton Thanks for the feedback on the naming of the seasonal releases and really appreciate you sharing your perspective. Happy to pass these feedback back to our partners in the Jira team. You’re right that these releases roughly align with our TEAM and TEAM EU events, with an additional release in…

Hi @Ben R & @Mathew Lederman Thanks for the suggestion! Google Forms is one of the tools we use today to gather initial interest. Once we get closer to early access, we’ll provide an actual signup portal through our legal consent management center instead. Happy to share the signup link here once it’s available.

Hi @Dave Mathijs oops, looks like the public link expired. The Loom link is now public again, thanks. 

Hey @Dave LIAO, thanks so much for your feedback! Absolutely—that’s exactly the direction we’re heading as we continue to improve and expand our change management features. 

Hi @Dave Liao ️ Thank you for your feedback! I'm happy to share that we're already working on this improvement and plan to release it in an upcoming iteration.

Hi @Joe Baldwin , thanks for your questions. The maximum period for deferring a rollout is typically around 30 days. Deferral is managed on a per-change basis. To view the exact deferral date for a specific new change, click the Defer button associated with that feature. Deferral of product changes is not reflected in…

Hi @Janelle Cashmere It may take some time for all the emails to be redelivered to our customers. Please let me know if you haven't received yours yet. Thank you again for your patience and understanding on this matter, and sorry again for any inconvenience this may have caused.

Hi @Janelle Cashmere Thank you for bringing this to our attention. Due to a minor internal issue, some admins may not have received the latest Bundle track emails. We will be resending these emails today and tomorrow. In the meantime, you can check the upcoming changes in the September bundle by visiting the Release Tracks…

Hi @Steve Davis Thank you for your feedback! Product updates is currently provided exclusively to org admins because the interface displays org-admin-specific information, such as release dates and feature rollouts across multiple sites. At present, site admins can access similar release notes through Atlassian's Cloud…

Hi @Yatish Madhav This feature is now fully released and ready for immediate use. To access Product Updates, navigate to admin.atlassian.com and then go to Products > Product Updates, thanks.