The Jira Align support guide provides an overview of the various help resources available for Jira Align, as well as guidelines for creating and monitoring support tickets, feature requests, and test instance refresh requests. We recommend reading this guide to assist you in creating better cases and getting issues resolved as quickly as possible.

Check it out in the Atlassian Community here.

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.

Below is our upcoming release schedule. Sandbox and production environments will be unavailable during our maintenance window, which starts at 11:00PM EST on the day listed below and ends at 2:00AM EST on the following day.

Release tracks

Production environments are set to use the bundled release track, while sandbox environments use the continuous track. We recommend using this default setup for your environments, as it allows you to test new features released in a .0 feature release for two weeks in your sandbox environment. Those changes will then deploy to your production environment in a .1 maintenance release. 

Jira Align's Enterprise Insights (EI) version 11.22 was deployed to environments on the continuous release track on February 27, 2026. It will then be deployed to environments on the bundled release track on March 13, 2026. The following changes are included in version 11.22:

Release highlights

Enhancements and features:

• Track export schema versions via manifest
  
  For data file retrieval Parquet exports, the manifest.json file now includes a release_version field. This allows you to see which Enterprise Insights schema version was used for a given export and align your downstream data pipelines accordingly.
  
  Example entry in the manifest: "release_version": "11.21.1.5761"
  
  Use this value to validate compatibility between exported data and any versioned transformations or reports in your data platform.

• Per-run manifest files for improved traceability

  For data file retrieval Parquet exports, Enterprise Insights now generates a separate manifest file for each ETL run in addition to the primary manifest.json file.

  ETL-ID-specific manifests are retained, providing a historical record of exports for audit and troubleshooting. The primary manifest continues to be overwritten on each run. 

  Per-run manifest naming pattern:

  manifest_etlid_{etl_id}_{timestamp}Z.json

  Example:

  manifest_etlid_12345_20260201_073741Z.json

  You can use these per-run manifests to trace individual ETL executions, validate which files were produced for a given run, and correlate exports with events in your downstream systems.

Bug fixes delivered in 11.22:

• JARDA-7727: Fixed a bug where multiple features show current_dw.Feature.[Date Created] = NULL while the corresponding Jira Align records have a populated created date.

Below is our upcoming release schedule for Enterprise Insights (EI). Sandbox and production environments will be unavailable during our maintenance window, which starts at 11:00PM EST on the day listed below and ends at 2:00AM EST on the following day.

See the Release calendar article for the schedule of releases for the Jira Align platform. 

To improve compatibility with data platforms that treat fixed-width character padding as significant, Enterprise Insights (EI) will change several column data types from NCHAR to NVARCHAR. This update prevents trailing and padding spaces from propagating into customer data warehouses and analytics tools, causing configuration and processing issues.

We plan to make this change to the Enterprise Insights schema in version 11.19, which first ships to environments on the continuous release track on December 5, 2025.

Please review this announcement to understand what’s changing, how it may impact your integrations, and what actions you need to take to prepare.

Why we’re making this change

We are changing the data type of several columns in EI to assure:

• Downstream compatibility: Some systems (such as Snowflake) treat trailing spaces as meaningful characters, which can break joins, filters, and equality checks.
• Data quality and consistency: NVARCHAR avoids automatic right-padding that occurs with NCHAR, reducing unexpected whitespace and the need for post-load trimming.
• Operational simplicity: Reduces edge cases in ETL/ELT logic, improves report accuracy, and simplifies cross-system mappings.

Impacts of this change

As a result of these data type changes, the next Enterprise Insights schema will include differences that may interfere with existing integrations, models, and tests if they assume fixed-width (padded) values.

How to prepare

To prepare for the data type changes, you can take the following actions:

• Review your downstream data models and dashboards for any explicit assumptions about fixed-width padding or trailing spaces.
• Remove redundant TRIM, RTRIM, or LTRIM steps that were previously used to compensate for NCHAR padding where they are no longer needed.
• Validate critical joins and equality predicates in Snowflake or other data warehouses to ensure they do not depend on padded values.
• If your schema enforcement or testing frameworks pin data types, update expectations from NCHAR to NVARCHAR for impacted columns.

Columns affected

Use the table below to review the columns that will change from NCHAR to NVARCHAR.

You can subscribe to three Help Center sections to receive notifications the instant release note articles are published:

• Main Release Notes: These articles contain compiled information on a Jira Align version, initially published for the 10.X.0 feature release and updated each additional release through 10.X.3.
• Supplemental Release Notes: These articles contain information on individual supplemental releases, published each release from 10.X.1 through 10.X.3.
• Enterprise Insights Release Notes: These articles contain release notes specific to Jira Align Enterprise Insights (EI).

We recommend subscribing to both the Main and Supplemental Release Notes sections to get weekly notifications on the latest Jira Align version.

What you need to do

To receive real-time release notes publication notifications, you'll need to create a Help Center account and follow the section or sections you want to receive notifications about. Please note, this will most likely be a different username and password than your Jira Align and Atlassian username and password. 

 To create an account (or reset your password if an account already exists), click the SIGN IN button on the Help Center (see the pink arrow).

Next, click the Sign up link, enter your name and email, and then click the Sign up button. You'll receive an email to finish setting up your account. If you receive a message that says a user has already signed up with the given email, click the Forgot my password link to reset your password.

Once logged in, from the Help Center home page, click the WHAT'S NEW section (bell icon).

Then click the header for the section you want to follow. Finally, click the FOLLOW button and then the New articles link.

That's it! As soon as we publish new release notes, you'll receive an email notification with a link!