Release notes for 11.19.X

Last updated: December 12, 2025 to include bug fixes delivered during the week

The Atlassian Jira Align team is pleased to announce Jira Align v.11.19. 

• Coming soon
• Enhancements and features
• Bug fixes

Coming soon

Upcoming removal of JET app

The JET app for Jira reached end-of-support (EOS) on September 17, 2025. We are still planning to remove access to the app, now targeting sometime in the first part of 2026. Once a specific removal date is set, we’ll make a future announcement. For more information on alternatives and how to track your Jira health, see our article in the Atlassian Community.

New Recycle Bin and Delete APIs coming in 11.20

In the 11.20 release, we’ll introduce a set of work item APIs that support both the recycle bin and deletion. If you have any questions or encounter issues using existing experimental APIs, please reach out to our support team.

Enhancements and features

These features for 11.19 were released to environments on the continuous release track on December 5, 2025, in version 11.19.0. The features will be released to environments on the bundled release track on December 19, 2025, in version 11.19.1.

Test out the beta epics grid experience

Our beta experience for the new epics grid page is now available! This enhanced version of the grid offers new, more usable ways to find and edit Jira Align epics. The new experience is available by default for all users in version 11.19.X. Access is controlled through the Portfolio > Epics (Beta) system role toggle. 

To access the new page, select the Epics Beta link from the sidebar after accessing a portfolio, solution, or program in the top navigation bar. You can also reach the page from the Items menu in the top-right corner of Jira Align.

In this first beta release, you can explore features like:

• A new, familiar grid table used by other apps like Jira. Add as many columns as you need and use infinite scroll to view all of your epics and their attributes.

• A redesigned, inline filtering experience with support for multiple operators on many fields.

• Access the page from an enterprise, portfolio, solution, or program navigation context.

• Export capability with support for selected fields and filters (work in progress)

• Support for deep-linking, providing you with a quick way to share a customized view with other team members.

Share your feedback

As you test out this new experience, we’d love to hear from you! The quickest, and most direct way is to use the Feedback button found in the upper-right corner of the page.

You can also comment and vote on the already created list of potential Epic Grid improvements on our suggestion site. If you don’t see your preferred improvement in the list, create a new suggestion with the following attributes:

• Project: Jira Align

• Component: Epics - Grid

Suggestions in Under Consideration status are on our near-term roadmap and are coming in the next versions. For the suggestion in Gathering Interest status, we are building the business case and gathering more data in order to decide which one will help the majority of customers the most and should be scheduled.

What’s coming next?

We plan to incrementally deliver the most needed improvements in the next few JA versions. You can track plans and progress by following updates in this suggestion ticket. Also, check out our community announcement for more details.

Enjoy exploring the new experience! Tell us what’s great, what’s tricky, and what would make your experience even better.

Beta roadmaps are now GA roadmaps!

As mentioned in the Atlassian Community, our new roadmaps, previously in beta, are now fully released and available to all users. This update brings enhanced stability and support, so you can confidently plan, track, and communicate your team’s work using roadmaps.

 

As part of this change and to ensure full support of the legacy roadmaps functionality, the program increment and release vehicle views accessible from the legacy roadmaps page have been moved to a new page. Find this page by navigating to a portfolio, solution, or program context, and then select Reports > Program increment and release vehicle roadmaps from the sidebar.

If you dont see the page active in your sidebar, ensure the Program > Manage > Program increment and release vehicle roadmaps permission is switched on for your system role.

Roadmaps: improvements to suggested dates

We’ve made it easier and more flexible to manage suggested dates on your roadmaps.

• Bulk save suggestions: You can now select and save up to 100 suggested dates at once. Use the new multi-select command, Select first X items, found in the bar at the bottom-right of the page, to quickly choose multiple suggestions for saving.
  

• Feature-level enhancements: Suggested dates for features now use the target completion sprint set on the program board. If a target sprint is assigned to a feature there, that sprint will be used as the suggested date. If no target sprint is set, suggested dates will continue to use the program increment as before.

Roadmaps: visual improvements

We’ve made several enhancements to the roadmap experience to help you visualize more data, navigate with ease, and focus on what matters most.

• Timeline view by year: You can now view your roadmap by year using the bar in the bottom-right of a roadmap, making it easier to plan and communicate long-term initiatives.

  

• Horizontal scrolling: Scroll across the Fields section to more easily view field information.

• Column limit increase: We’ve expanded the number of columns you can view on a roadmap to 11 columns.

• Focus areas column: A new Focus areas column is now available in the grid. This lets you bring in data directly from Focus, making it easier to view and organize work by strategic priorities.

Roadmaps: anchor sprints now visible

You can now display anchor sprints directly on your roadmap, giving you a clear view of key milestones and alignment points across teams and program increments. When enabled, you’ll see two bars on your roadmap columns, grouping the anchor sprints according to their program increments. Selecting an anchor sprint will open the parent program increment’s details panel, where you can view the anchor sprints in the Sync Sprints tab.

You can enable this feature with the Show Anchor Sprints toggle in View settings.

Roadmaps: view story and children counts

We’ve enhanced roadmap accuracy and transparency with two updates:

• Story counts: See at a glance how many child stories are assigned to sprints while viewing features, helping you gauge scope and progress. You can enable this feature with the Show story counts toggle in View settings.
  
  Once enabled, you'll see a color-coded count of stories on a feature's item bar, lined up on the timeline with the date of an anchor sprint. Only stories that are associated with sprints will be included in the count. If a story is associated with a sprint that has dates outside of the feature's start and end dates, the count will display in red. 

  

• Child count tooltip: We’ve added a new tooltip to the Children column to reduce confusion about why the children count may differ from the expanded content on the roadmap. The count may be more than what’s shown due to your system role permissions and page filters.

Roadmaps: group by release vehicle

You can now group items on your roadmap by release vehicle, making it easier to organize, visualize, and track work according to delivery milestones. Find the new option in the View settings menu on feature roadmaps.

Backlog: Process Flow view disabled for enterprise, custom room, and product navigation

The Process Flow view is no longer available when accessing the backlog from enterprise, custom room, or product navigation contexts. This ensures that users only see supported views for these navigation levels.

If you attempt to access the process flow (value stream) view directly using a URL at these levels, you’ll be redirected to the standard backlog list view for that context.

Bug fixes

Last updated: December 12, 2025

This list of resolved bugs will be updated weekly to reflect changes from maintenance and bug fix releases.

We’ve corrected the following bugs that were discovered while investigating related issues, building new enhancements, and performing maintenance:

11.19.0

• Change logs would display incorrect Jira connector IDs when updating the configuration for any connector besides ID number 1.

• API start and end times weren’t properly converted to Cootdinated Universal Time (UTC).

• In the API, users couldn’t update objectives with a link that had a null Link property.

• When an epic’s title contained angle brackets (< >), selecting the Benefits tab would result in a “Whoops” error.

• Users who weren’t super users couldn’t query the DetailsPanelsSettings API endpoint.

• On roadmaps, the Health dropdown options weren’t fully visible when opening the dropdown on the last listed item.

• On roadmaps, vertical scrolling wasn’t working correctly.

• On roadmaps, updating a feature’s start and/or end date wouldn’t update the story count color.

• On roadmaps, selecting a story card wouldn’t open the story’s details panel.

• On roadmaps, users couldn’t bulk accept suggested dates on the program objective roadmap.

• On roadmaps, users would have to refresh the page to view changes made in Suggest Dates mode.

• When bulk accepting roadmap items, the resulting message would display an incorrect count of items that were changed.

• We fixed a capitalization error for the Suggested date label on the roadmap legend.

• Users couldn’t change their subscription status on objectives.

• Custom field values would disappear after adding a comment to a dependency.

• On kanban boards, users couldn’t move stories without team assignments to the Accepted state.

• On kanban boards, an error message wouldn’t display when mass adding too many items to columns with WIP limits.

• When opening the backlog’s value stream Kanban view, the state view would display instead.

• On the feature backlog, features would disappear if their child story’s details panel was closed.

11.19.0.1209

• In the API, users with the correct permissions were unable to create or update iterations without a super admin token. 

11.19.1

• On the beta epics page, non-super admin users who had access to an epic through its additional program assignment couldn't see story points on the grid.