Release notes for 11.22.X

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

• 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.22 were released to environments on the continuous release track on February 27, 2026, in version 11.22.0. The features will be released to environments on the bundled release track on March 13, 2026, in version 11.22.1.

Test out the beta features grid experience

Our beta experience for the new features grid page is now available! This enhanced version of the page offers new, more usable ways to find and edit Jira Align features, and builds on the enhancements provided by the new epics grid page.

 

The beta features page is disabled by default and can be enabled by switching on the Program > Features (Beta) system role toggle.

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

Note: When navigating from a portfolio or solution, find the Features Beta link in the More items section of the sidebar.

In this first release, you can explore:

• A modernized features page
• 43 columns
• 23 filters
• 11 sorting options
   

 

Not yet supported

• Export, import, and workflow actions
• Filtering operators such as is, is not, or searching for empty values

The new epics grid page graduates from beta

The updated epics grid page is now generally available (GA). We’ll continue enhancing the experience in upcoming releases.

• Access both experiences: For now, both the legacy and new epics grid pages will remain available. We’ll share a future transition date once we’re ready to end support for the old experience.
• On-premises environments: After you install Jira Align 11.22.x, you can enable the new epics grid page by contacting Atlassian Support. We’ll make the new page available by default in a future version of Jira Align on-premises.

 

The new epics page can be enabled or disabled with the Portfolio > Epics (New) system role toggle.

Grid pages: store and retrieve your customizations with saved views

We’re excited to introduce the ability to save views on the new epics grid page and beta features grid page. A view saves your filters, sorting, and display options so you can quickly return to a curated grid between sessions.

Capture your current filters, layout, and columns by clicking the Save view option at the top of the page.

You can create multiple saved views. Each view is unique to you, allowing you to create shortcuts for your most-used configurations. Find your saved views in the new Views menu, where you can open a view, edit a view name, or delete a view.

After accessing a view and making changes to the filters or other display settings, you’ll see an option to update the view, or save a new copy.

Grid pages: level-specific UI memory

When you leave and then come back to the new epics grid page or the beta features grid page, you will find each page in same state you left it. All filters, sorting, and columns will be retained from your previous visit.

A state memory is retained for each team hierarchy level: portfolios, solutions, and programs. When you moves across team levels through navigation, you access a different state.

For example, if you’ve recently visited the epics page from a portfolio and enabled the Theme column, then navigated to a program epics page where you enabled the Tags column:

• Switching between portfolios A and portfolio B would keep the grid the same. The theme column displays on both pages.
• Switching from a portfolio to a program changes the grid, displaying the tags column instead of the theme column.

Grid pages: new columns, sorters, filters and operators

New columns

• Release Vehicle
• Custom Text Area
• Custom Text
• Custom Dropdown
• Custom Multi-Select Dropdown

New filters

• Custom Text Area
• Custom Text
• Custom Dropdown
• Custom Multi-Select Dropdown

New “no value” filtering option

We’ve added the “no value” value as a filtering option for the following epic attributes:

• Customer
• Investment Type
• Process Step
• Strategic Driver

New sorting options

The following columns can now be sorted on the page:

• Age
• Custom Text Area
• Custom Text
• Custom Dropdown
• Theme

Grid pages: total count of epics

The total number of epics is now available at the bottom of the page. When there are fewer than 1000 epics meeting your filter criteria, the exact number is displayed instantly.

When the total number of epics is larger than 1000, a selectable link is displayed.

Select the link to see the total value. This on-demand total functionality helps to keep the page loading quickly.

Roadmaps: dependency data

You can now bring dependency status directly into your roadmap views.

• Add the Impacted by Dependency column for epics, capabilities and features. Work items that are impacted by an existing dependency will display Yes.
• Add the Assigned to Dependency column for capabilities and features. Work items that are assigned to an existing dependency will display Yes.
  • Note: This column can be selected at all levels for UI consistency, but dependency data is only populated for capabilities and features.
• You can filter by both of these new fields with compatible work item types in the roadmap.
• These new columns and filters are preserved when sharing roadmap deep links and saving views.

Roadmaps: additional display and filtering options

We’re continuing adding more improvements and options to the filtering experience on the roadmaps page.

New parent column

Add the new Parent column to your display to see each work item’s parent, displayed as a selectable link.

New filters

We’ve added multiple new filter options with different operators:

• Theme for capabilities and features with “is” operator
• Strategic Driver for epics with “is” and “is not” operators
• Id for epics and features with “is”, “is not”, “contains”, and “doesn’t contain” operators
• Type for epics and features with “is” and “is not” operators
• Approach type for features with “is” and “is not” operators

New “is not” filtering option

We’ve added the “is not” value as a filtering option for the following epic attributes:

• Owner
• State
• Customer
• Theme
• Investment Type
• Process Step
• Portfolio
• Primary Program

New sorting options

The following options are now available to sort your roadmap view when using the Sort by menu found in View settings:

• Age for epics and features
• Id for epics and features
• Created Date for epics and features

Roadmaps: global UI memory

When you leave and return to roadmaps, you will now find the page in same state you left it. All filters, sorting, and columns will be retained from your previous visit. Your configuration stays consistent across the roadmap experience, so you can continue where you left off without saving a view first.

Notes: 

• Roadmaps use a global state memory for all levels of team hierarchy. Navigating to the page from a different portfolio, solution, or program will continue to display the same state.

• Changing the work item type being viewed will clear any existing filters.

Updated terminology to support Jira spaces

Jira recently changed ‘projects' terminology to 'spaces,' to better reflect the diverse ways teams define and manage their work in Jira. In this release, we’re rolling out those same changes for Jira Align.

All instances of “Jira project” terminology have been updated to “Jira spaces.” This includes the Jira settings and management pages, work item slideouts, filters, and logs. This change is purely a terminology change – everything else about how you use these containers remains the same.

There are no changes to existing APIs or the Enterprise Insights schema; they will continue to function as they currently do.

This change was made for all types of Jira connectors, Cloud and Jira Data Center.

Parent column when prioritizing capabilities and features

We’ve added a new parent column and supporting filter to the capability prioritization and feature prioritization pages, so you can quickly see the next level of hierarchy when estimating work.

The pages now show a selectable parent name for each item, opening the parent’s details panel so you can review or adjust context without leaving the estimation view. For standalone items without a parent, the column displays a set of dashes, making it easy to distinguish them during WSJF or sizing discussions.

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

• Identified and resolved a vulnerability related to story reviews.
• Identified and resolved a vulnerability related to creating team sprints.
• On the release vehicle roadmap report, the capture option was not functioning.
• Users with the correct permissions were not able to create ideation groups.
• On the stories grid page, drag and drop ranking of acceptance criteria was not saving.
• Platform terminology was not correctly displayed in alert messages when creating sprints from a program increment details panel.