Release notes for 11.16.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated October 3, 2025 to include bug fixes delivered during the week

Coming soon

Upcoming GA of beta roadmaps and removal of legacy roadmaps

We are excited to announce that the beta roadmaps experience will move to general availability (GA) status in an upcoming release. As a result, we are setting a timeline to remove the legacy roadmap page.

We plan to make new roadmaps experience the default, and remove the legacy experience as soon as version 11.19.0, scheduled to begin deployments December 5, 2025. As we evaluate this schedule, we may set a later date for transition. Keep an eye on each set of release notes from now through the end of 2025 for updates.

Review our community announcement for details on the transition, and further planned enhancements as part of GA.

Upcoming end-of-support (EOS) status and removal for JET app

The JET app for Jira will be designated with end-of-support (EOS) status as of September 17, 2025. We then plan to remove access to the app sometime before December 31, 2025. We’ll provide updates on this timeline in future release notes. This removal is to support Atlassian’s EOS plan for marketplace apps built with Connect.

Enhancements and features

These features for 11.16 were released to environments on the continuous release track on September 12, 2025, in version 11.16.0. The features will be released to environments on the bundled release track on September 26, 2025, in version 11.16.1.

Beta roadmaps: New columns and filters

You can now add two new columns to your roadmap’s view, giving you greater flexibility, and more details about work you’re planning:

• Tags
• Blocked

Additionally, we’ve introduced two new filters, making it easier to focus on the work that matters most to your team:

• Release vehicle for features
• Theme group for themes

Beta roadmaps: New sort options

Use the following four new options in the Additional settings Sort by dropdown to organize roadmap items further:

• Blocked for objectives and features
• Theme Group for themes
• Custom text fields for all work items*
• Custom dropdown fields, single-select for all work items*

Note: Custom fields must be active to be available as a sort by option. When viewing a roadmap from the enterprise level, only theme custom fields are available.

Beta roadmaps: Visibility and usability improvements

When reviewing columns that contain multiple values, you can now hover in a cell to see the full list of entries. Previously, this interaction required you to select a cell to see additional values.

We've also made some changes to settings menus to improve usability and consistency:

Columns

The Columns menu interface now matches the same toggle format used by the View settings menu, as well as timeline experiences in Jira. Use the new Search field to quickly find a column.

We’ve also improved the experience when attempting to display more than the maximum of 6 columns. Additional values cannot be switched on once 6 fields are displayed.

View settings

The View settings menu has been re-organized and labeled for better separation of different functionality.

In the Display section, you can manage visibility of program increment labels and milestones. The Categorization section is where you can see data by roadmap item attributes. Sort by is the current option in the section, and we plan on bringing more features like group by, and color by.

Beta roadmaps: Give feedback button

Use the new Give feedback button on the beta roadmaps page to quickly give us feedback in the moment. We’re planning to graduate the experience near the end of 2025, replacing the legacy roadmaps page. Let us know what’s most important to your teams to use new roadmaps exclusively in the coming months.

Work items: Improved support of text types and strings in Description fields

We’ve started work on one of the highest-voted connector issues, and in this release, story descriptions with code snippets or specific text strings will no longer create invalid errors on save.

This issue was primarily occurring when syncing code snippets or specific text strings from Jira or ADO connectors to Jira Align, due to a network configuration blocking description text.

Improved support for capabilities and epics is also planned for an upcoming release.

External reports are now editable custom reports

We've renamed the external reports page to custom reports, as we prepare to further re-imagine this capability. The new name indicates support for both inside and outside the Atlassian platform, including Atlassian Analytics dashboards.

You can also now edit an existing custom report to quickly make modifications to links or queries:

Help message when attempting access with Internet Explorer

To provide more clarity for users who attempt to access Jira Align with Internet Explorer, we’ve added a redirect page that explains that this browser is not supported. This update helps users quickly identify which browsers are compatible, and guides them to switch to a supported option.

Review Jira Align’s browser support policy for more details

Bug fixes

Last updated October 3, 2025 to include bug fixes delivered during the week

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.16.0

• Identified and resolved a vulnerability related to custom reports.

11.16.0.0924

• Milestones for child roadmap items would not display in beta roadmaps until a page refresh.

11.16.0.0925

• No error message was displayed when failing to save a work item subscription due to a permissions error.
• Identified and resolved a vulnerability related to work item states.
• Identified and resolved a vulnerability related to subscriptions.
• Identified and resolved a vulnerability related to team-level permissions.

11.16.1

• Identified and resolved a vulnerability related to the Why button.
• Identified and resolved a vulnerability related to link maps.

11.16.1.1001

• Identified and resolved a vulnerability related to checklists.