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.
29 comments