Release notes for 11.23.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Coming soon

Early access program: Rovo in Jira Align

We’re excited to announce that Rovo, Atlassian’s AI-powered assistant, is coming soon to Jira Align! With this enhancement, you’ll be able to chat with Rovo directly in Jira Align and ask questions about your organization’s data to get instant insights.

Early access will be available through a beta program running from February 2nd through March 31st. Participants will help shape the final experience and receive dedicated support. Your feedback during the beta will directly impact how Rovo evolves in Jira Align.

To join the early access program, contact your Advisory Services representative, or open a new request with Atlassian Support, titled Align Rovo early access.

Enhancements and features

These features for 11.23 were released to environments on the continuous release track on March 27, 2026, in version 11.23.0. The features will be released to environments on the bundled release track on April 10, 2026, in version 11.23.1.

Share your saved views with others

You can now share your customized view with teammates and other users on the roadmaps, new epics grid, and beta features grid pages.

When creating or editing a saved view, choose a visibility setting:

• Private is the default, and keeps the view accessible only to you.
  • A lock icon displays next to the view name in menus and the page title.
• Public lets other users access the view from the page’s Views menu.
  • The creator’s name and avatar will be displayed in the More actions menu, allowing others to identify a view owner.

Permissions to save and modify public views are based on two new system role permission toggles. By default, only the Super Admin role has these new permissions enabled at launch:

• Additional options > Allow to save public view
  • Provides the ability to save a view as public.
• Additional options > Allow to modify non-owned views
  • Provides the ability to edit and delete public views created by others.

Roadmaps: sort features by program ranks

You can now sort features on roadmaps using the same ranking order defined in your feature backlog, giving you a consistent view of priorities across planning surfaces.

• Program Rank: When viewing features at the program level with no program increment or multiple PIs selected in the side navigation menu, select the new Program Rank sort option from the Sort by dropdown in View settings. Features will display in the same order as they appear in your feature backlog for that program.
• Program PI Rank: When a single PI is selected in the side navigation menu, the sort option automatically switches to Program PI Rank, reflecting the backlog ranking for that specific program increment.
• Unranked features display at the bottom.
• Sort options respect your platform terminology and are preserved in deep links for easy sharing.

Roadmaps: sort capabilities by solution ranks

Similar to program rank for features, you can now sort capabilities on roadmaps by solution rank to align your roadmap view with your capability backlog priorities.

• Solution Rank: When viewing capabilities at the solution level with no PI or multiple PIs selected in the side navigation menu, select the new Solution Rank sort option from the Sort by dropdown in View settings. Capabilities will display in the same order as they appear in your capability backlog for that solution.
• Solution PI Rank: When a single PI is selected in the side navigation menu, the sort option automatically switches to Solution PI Rank, reflecting the backlog ranking for that specific program increment.
• Unranked capabilities display at the bottom.
• Sort options respect your platform terminology and are preserved in deep links for easy sharing.

Roadmaps: improved custom hierarchy permissions

We've improved how role toggle permissions work for custom hierarchies and the new roadmap, making it easier for administrators to grant the right level of access without over-provisioning.

• More granular access for roadmaps and custom hierarchies: The Administration > Roadmaps (New) for Custom Hierarchies system role toggle can now be enabled even if the main Custom Hierarchies toggle is disabled, as long as the role has view access to at least one custom level.
  • Previously, enabling roadmaps for custom hierarchies would automatically turn on the Custom Hierarchies toggle, granting the ability to create and edit custom hierarchy levels. Administrators can now grant roadmap access to custom rooms without also granting custom hierarchy administrative permissions.
• Custom hierarchy columns and filters available to all users: Custom hierarchy columns and filters on roadmaps are now visible for all roles and no longer require the Custom Hierarchies system role toggle to be enabled. This brings roadmaps in line with other areas of Jira Align, where users can already see and access custom rooms and custom hierarchy values in work item details panels regardless of this toggle.

Epics grid page: edit dates inline

You can now edit date fields inline on the new epics grid page, using the same interaction found on roadmaps. This gives you a quick way to prepare multiple epics for planning discussions.

Select a Start/Initiation or Target Completion cell to open a date picker. Once you’ve selected a date, tab or select away from the cell to save your choice.

Epics grid page: Release vehicle column

You can now add the Release vehicle column when viewing the new epics grid page.

Program increments: consistent planning across mixed-capability hierarchies

Previously, Jira Align required separate program increments for portfolios that use capabilities and portfolios that don't. If your instance had a mix of both, you couldn't assign a single program increment across them, forcing teams to create and manage duplicate PIs for the same planning period.

Now, a single program increment can be assigned to any portfolio regardless of its capability configuration. This works across both the UI and the public API.

Other enhancements included with this change:

• Accurate Strategy Room rollups: Previously, rollups when grouping by PI were driven by the primary portfolio's capability setting, which could produce incorrect results for mixed configurations. Rollups now respect each portfolio's individual settings.
• Correct PI slide-out details: The Program Increment slide-out now shows the Capability tab and calculates progress only for portfolios where capabilities are enabled.
• Backlog views that match your hierarchy: When viewing by PI, the backlog now displays the correct child work item type: epics for non-capability portfolios and capabilities for capability-enabled portfolios. Previously, mixed PIs could incorrectly show "no features" for portfolios where capabilities should have been listed instead.

API: New endpoints for forecasts

We’ve introduced a new set of Forecasts Public APIs so you can programmatically read and manage forecast estimates for Jira Align work items, making it easier to keep external planning tools and reports aligned with what’s configured in Jira Align.

• Work across key portfolio items: Access forecasts for epics, capabilities, and features, with support for release‑level, program‑level, and team‑level forecasts on each work item.
• Read and write forecasts via API: Use GET endpoints to retrieve existing forecasts, and POST/PUT endpoints to create or update program and team forecasts where applicable, following the same validation rules as the Forecast tab in the UI.
• Support multiple estimation systems: Send and receive estimates in points or member/team weeks; when the portfolio is configured for T‑shirt sizing, the API uses member or team weeks as the numeric representation behind those sizes.
• Respect permissions and data integrity: All endpoints honor Jira Align permissions and Forecast tab access. Attempts to edit estimates that are retained from past program increment assignments are blocked and return a 409 Conflict, ensuring historical data remains read‑only.
• Handle large data sets with pagination: Bulk GET endpoints support skip and top query parameters so you can iterate through large collections of forecasts efficiently.

Beta features grid page: new abilities, filters, and operators

We’ve made the following enhancements to the beta version of the features grid page:

• Export support: Find the Export option available in the More (…) menu, providing parity with the legacy features grid.
  • Custom Hierarchy columns are now included in exports, with each hierarchy represented as its own uniquely named column.
• Setup workflow support: Find the Setup workflow option available in the More (…) menu, providing parity with the legacy features grid.
• New filters: Use the following filters to find specific features for your team and work.
  • Release vehicle
  • Category
  • Custom hierarchy
• New filter operators: Use the following operators when filtering to identify specific features you care about.
  • Not in operator for
    • State
    • Portfolio
    • Solution
    • Primary program
    • Programs
    • Owner
    • Approach
    • Category
    • Customer
    • Product
    • Theme
    • Process step
    • Custom hierarchy
    • Custom single dropdown
    • Custom multi dropdown
  • No value operator for
    • Portfolio
    • Solution
    • Theme
    • Customer
    • Product
    • Program increment
    • Tag
    • Process step
  • Filters for custom text input and custom text area fields now support the Is, Is not, and Doesn’t contain operators.
  • Filters for custom multi dropdown fields now support all operators, providing full parity with other dropdown filters.

Bug fixes

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

• In the API, the mapped process step was not set on epics and capabilities when only state was provided in POST calls.
• Identified and resolved a vulnerability related to canvases.
• Identified and resolved a vulnerability related to program increments.
• On the roadmaps page, work items were not displaying after filtering by theme = no value.
• On the epics grid page, results were not displaying after filtering by process steps associated with additional programs.
• On the epics grid page, confirmation messages were not displaying after deleting an epic.
• On the epics grid page, users could not see the name of some parent themes.
• On the epics grid page, keyboard navigation was not functioning when searching and selecting views.
• On the epics grid page, selecting a work item's name from the discussions modal would not open a details panel.
• On the epics grid page, filtering by name with the "_" character would not display results.
• On the epics grid page, filtering by process step = "no value" would not display results.