Beta no more, new roadmaps are going GA

[#1]

Hello Jira Align community!

We’re excited to share a major milestone in our journey to reimagine planning at scale: the new Jira Align roadmap experience is preparing to move from beta to general availability (GA)! This update brings a more intuitive, performant, and flexible way to visualize and manage your strategic plans—built on your feedback and the evolving needs of modern enterprises.

Thanks to your input, we've improved the beta roadmaps experience over the past three months. Here's what we've shipped, including today's 11.16 release:

• Inline date editing: Update dates directly from the roadmap view for faster, more intuitive planning.

• Suggested dates mode: Quickly fill in missing dates with system-suggested values, streamlining initial setup.

• Progress tracking: Visualize completion status for roadmap items at a glance, and in detail, helping teams monitor delivery.

• Global rank sorting: Sort roadmap items by global rank to better reflect organizational priorities.

• Performance improvements: Continued backend optimizations for faster load times and smoother interactions, especially on large roadmaps.

• New columns and filters: View and filter roadmap items by tags, blocked status, release vehicle, and theme group for more granular control over your roadmap views.

• Bug fixes and reliability: Addressed many of the top-reported issues to ensure a more stable and reliable experience.

Timeline & transition plan

We plan to make the new roadmap page the default experience for all cloud environments in either version 11.19.0, which first deploys to environments on Dec 5, 2025, or one of the next versions in early 2026. We’ll provide updates on this plan in each of the following release notes between now and the end of 2025.

Once the new experience is default, access to the old roadmaps page will no longer be available.

If your organization needs access to the old roadmaps page for a short, additional period of time after the planned transition, submit an Atlassian support request with the title “Extend roadmap transition.” We may provide continued access to the old experience for up to 90 days after the confirmed transition date.

What's next?

We’re not done yet! We plan to ship a few more key enhancements as part of graduating new roadmaps to GA:

• Group by functionality: Organize roadmap items by various attributes for clarity and management.

• Color by options: Use color coding to quickly identify different categories or statuses within your roadmap.

• Additional metadata: Critical fields that help you slice and dice work like custom hierarchies, notes, custom fields, and more are coming to the new roadmap as columns, filters, and sorts.

• Enhanced sprint associations and story information: Improve alignment and track which stories are happening in which sprints for better visibility and management.

These enhancements are aimed at providing a comprehensive toolset for organizations to effectively plan, track, and deliver their strategic initiatives.

Join the conversation

We want to hear from you as you navigate the new roadmap experience. Your insights not only help us refine the current features but also guide our future developments. Use the new Give feedback button in the upper-right of the roadmaps page to let us know how we can improve.

[Graeme Wright]

Please don't deprecate the legacy roadmap views until

a) timeline bars will render using the Program Increment start and/or end dates if no Target Start and/or Target Completion dates are specified

b) Program Increment view shows the sprint/story detail on the bars similar to the current red/green boxes

Both these features of the legacy roadmap are widely used in our organization.

[Danny Presten]

I love new features but I'm concerned you're deprecating the existing roadmap without establishing parity. There are several features in the roadmap that are incredibly helpful (like the view that shows how many stories are in each sprint). Please don't take away functionality! I don't understand why you would release something "new" that seems to have less overall functionality.

[Ryan Reed]

Please do not deprecate the existing roadmaps until you have reached parity or near parity with the functionality of the existing roadmaps.