Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
I do like the concept here, but my honest first reaction was "I hope this doesn't mean we get critical improvements less often—I just want different priorities in what gets released first."
I'm hoping this shift helps unlock some resources for continuous releases around the foundational workflow issues that create real enterprise pain points.
Some examples:
We lack tools to easily clean up and reorder statuses in gadgets/functions, or merge duplicate statuses so our entire organization can speak a common language
Multi-space automation rules could benefit from space admin control so they can unlock more cross-space collaboration
And while I know there's work happening on aligning team-managed spaces, the proliferation of duplicate fields and inconsistent usage patterns across the organization has been challenging
I see real value in making the user-facing features and UI changes seasonal—that predictability will help with change management. But the underlying plumbing issues, including customer suggestions in JAC with many votes? Those feel like they need continuous attention rather than being bundled into quarterly cycles. And maybe that is your plan.
Maybe I'm hoping for the best of both worlds: seasonal releases for the shiny stuff, but ongoing fixes for the administrative and enterprise workflow foundations.
And I should also add that this is really great that you are reflecting on the status location move oversight, making some changes to help, and thinking about it holistically! There has been focus in the areas that effectively move the needle a lot for you all. A lot of the work that @Carol Low (and others) are currently doing in the Jira admin sections has been really helpful to assist us in cleaning up data sprawl and tighten the ecosystem to extract more value out of Jira for all new users!
Just echoing a lot of other comments - would love a bit more clarity on:
- how this fits with the current bundled/continuous release tracks? Is it replacing them entirely? As someone who governs many instances, I would still like options (seasonal, bundled, continuous?)
- will there be unification of release notes?
As an additional ask, it would be great if Rovo chat can be kept up to date on release notes as well, such that we can ask for summaries and set up automation rules (eg, to make change tickets or confluence pages).
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
Hi @Dave Meyer . Are these seasonal releases strictly for Jira (formerly JSW/JWM) or do they apply to the broader Jira family, such as Jira Service Management and Jira Product Discovery?
I haven't had a problem with the frequency of Jira changes, it's the quality. If it kept continuously updating with improvements that would be great. The problem is constant changes that break my workflow while delivering zero benefits.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
I completely understand why admin-types are worried about trying to keep track of all the changes, but for the average user, is there going to be some kind of filter on this to limit it to widespread changes or what an organization will be adopting?
🌟 As long as you have anactive Atlassian account with access to Jira, you will receive all updates pertaining to each seasonal release. 🌟
Given the current state of ads on Jira, I could see this setting off a nightmare barrage of unintentional user requests for products/features our organization is intentionally not adopting or not adopting yet. There's also the confusion between how Atlassian presents a feature and how organizations actually use them (think Projects vs. Spaces).
Can you explain which user levels will get which updates or provide previews before sending communications to our teams so we can try to tell them which pieces to ignore?
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
I'd love to live in a world where this isn't needed, but I really appreciate y'all taking this hard but absolutely necessary step. One ask: please make double-check that everyone internally is still opted into notifications...it seems that someone has managed to miss one already.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
@Dave Meyer I'd still like to advocate for not taking a fragmented approach to how product releases tracks are handled. This change seems to only impact Jira, and many customers use multiple Atlassian products like JSM, JPD, and Confluence. Moving to a seasonal release cadence for only one product will actually increase the complexity for customers who have other products on continuous release cycles.
We would greatly appreciate it if you could spend some extra cycles listening / learning before rolling this out. I fear this is going the path of the status menu change that was (thankfully) rolled back just a few months ago...
33 comments