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.21.
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.
Epics grid general availability
We’re excited to announce that the epic's grid general availability release is coming, expected in version 11.22.1.
All critical bugs are fixed, and you can expect some new features, too:
Custom fields support
Additional operators and sorters
Showing the number of epics at the end of the table
Features grid beta
We are happy to announce that a beta features grid is coming, expected in version 11.22.1. It inherits all the new great UX from the modernized epics grid. You’ll be able to explore:
A modernized features page
More than 30 columns
Over 20 filters
~10 sorting options
New dependency columns and filters on roadmaps
In version 11.22, you’ll be able to view work items based on their dependency relationships in roadmap, with new columns and the ability to work items by whether they are impacted by or assigned to a dependency. Opening a work item’s slideout will also show details about its related dependencies, giving you more comprehensive information.
These features for 11.21 were released to environments on the continuous release track on January 30, 2026, in version 11.21.0. The features will be released to environments on the bundled release track on February 13, 2026, in version 11.21.1.
Beta epics grid enhancements
We’ve made several improvements to the beta epics grid.
Focus Areas column: When Atlassian Guard is used, this new column will display, showing epics linked to focus areas in Focus.
Export improvements: Exporting now supports the browser’s loading indicator and includes portfolios and solutions columns. We also removed issues what would occur when special characters were used in platform terminology
Filters UX: Long filter options now display the full name on hover, and selected options are highlighted in the filter bar.
Feedback form: The feedback form is now deactivated if email isn’t set up.
New roadmap filtering experience
We’ve refreshed the look of roadmap filters to align with the new grid filtering experience. The new filtering UI is now consistent across all navigation levels and work items, making it easier to recognize and use filters throughout the roadmap.
Assign multiple capabilities to a dependency
You can now assign multiple capabilities to a single dependency, making it easier to track complex relationships across your work.
We’ve updated the dependency and capability details panels to support assigning multiple capabilities to a dependency.
We’ve restored the ability to add dependencies directly from the feature and capability details panels for faster planning.
The dependencies page now includes count columns for assigned stories, features, capabilities, and total assigned, giving you a clearer overview.
We also made updates to the dependency matrix, API, and Enterprise Insights to support this expanded functionality.
Filter by investment type on roadmaps
You can now filter epics by investment type on the roadmap. This new filter is available exclusively for the Portfolio Epic work item type, helping you quickly focus on epics that match specific investment categories.
Unplanned work warnings on roadmaps
It’s now easier to spot unplanned child stories for your features. A warning icon now appears in the Children column when a feature has child stories that are missing either a team or a sprint assignment. This helps you quickly identify and address stories that aren’t fully planned.
Retaining feature, capability, and epic estimates
Previously, when removing planning intervals from features, capabilities, and epics, estimates associated with those work items were removed. Now, when removing a planning interval, users can still reference those estimates in the respective work item forecast tab.
In the example below, the feature was originally assigned to QI-5, and team and program-level estimates were captured for QI-5. Then, the feature was moved to QI-6. As you can see on the forecast tab, the QI-5 estimates still show under the Previous Estimates section. You can easily reference the estimates and move them to QI-6 if needed.
A few additional notes on this functionality:
If a previously assigned planning interval with estimates is reassigned to the work item, the estimates will be restored.
For features, the planning interval, program, and team-level estimates are all restored.
For capabilities and epics, only program and team-level estimates are restored in this release. In an upcoming release, the planning interval-level estimates will be restored too.
Estimates associated with previously assigned planning intervals are not included in any calculations. They are displayed for reference purposes only.
If you want to remove the estimates associated with previously assigned planning intervals, that planning interval must first be added back to the work item.
New APIs to automate field management and Jira connector tasks
We’re completing the rollout of APIs for the following tasks:
Custom field management: Now, you can use APIs to create new custom fields and manage existing fields. For example, you can use APIs to keep the values in custom dropdown fields in sync with other systems of record.
System dropdown field management: In platform settings, there are a number of system dropdown fields that can be customized. Now you can use APIs to manage the values in these dropdowns, as described above.
Details panel settings management: As you roll out Jira Align to new teams or new functionality and fields, you no longer need to manually turn fields on/off or mark them as required/not required. You can use the details panel settings APIs to automate these tasks.
Jira connector custom sync jobs: A common task when integrating new Jira workspaces or mass updating Align data through the Jira connector is to run a custom sync. Now, you can use APIs to run custom sync and find the status of a previously run custom sync. In combination with the other Jira connector APIs already released, you can now fully automate the integration of new Jira workspaces.
This list of resolved bugs will be updated weekly to reflect changes from maintenance and bug fix releases.
| Key | Summary | Release Version |
| JIRAALIGN-7896 | Jira Connector - Stories breaks sync when have special Character in Custom Team mapping | 11.21.0 |
| JIRAALIGN-8649 | Jira DC Connector causes extra tags to appear when a Sprint Goal contains rich-text formatting | 11.21.0 |
| JIRAALIGN-8664 | Features not accessible when linked to non-existent Programs | 11.21.0 |
| JIRAALIGN-8739 | Roles without Feature delete option are able to delete a feature work item | 11.21.0 |
We’ve corrected the following bugs that were discovered while investigating related issues, building new enhancements, and performing maintenance:
11.21.0
On roadmaps, the Update View and Save as Copy buttons would improperly display when viewing a roadmap at the enterprise level.
On roadmaps, themes users didn’t have access to would display in the filters when opening a roadmap from a deeplink.
Opening a roadmap from a deeplink while using the Suggest dates feature would remove applied roadmap filters.
On roadmaps, the list of saved views wouldn’t update after a saved view was deleted.
Fields that were added when copying epics, capabilities, features, and tasks weren’t reflected in audit logs.
In the API, an error would occur when creating themes with a non-Super Admin with no access to the programIds provided in the request.
Users couldn’t remove links from the epic and capability details panels.
Identified and closed a vulnerability related to Jira Align integrations.
Identified and closed a vulnerability related to the program board.
Links to the beta epics page would have an incorrect icon when added to starred pages.
On the beta epics page, the vertical scrollbar would incorrectly move when an epic was created or deleted.
Epics that were copied with their children wouldn’t display on the beta epics page.
On the beta epics page, filters with long names didn’t have a hover message to view the full filter name.
The Epics (Beta) option would display on the sidebar when users didn’t have permission to view epics.
On the beta epics page, epics wouldn’t export if No value was selected in the Theme filter.
On the beta epics page, epics wouldn’t export if the Theme filter contained an Is not operator.
On the beta epics page, all sidebar options would display as selected when opening the page from a non-global context.
The Process Step filter wouldn’t apply when viewing all epics on the beta epics page.
On the objectives page, selecting Previous Page while on the last page of the grid would send users to the first page.
On the objectives page, when searching team objectives, users could only search for programs within the first 99 available programs.
Non-Super Admin users who only belonged to a dependency’s requesting team could uncommit the dependency.
Removing a dependency’s assigned item wasn’t reflected in audit logs.
Resolved some alignment and capitalization errors on the dependency details panel.
In the list of assigned items on a dependency, the text Show 5 more would always appear at the end of the list, even when there were no more items to show.
When a dependency was opened from a feature’s details panel and then closed, the dependency details panel would remain open and the feature’s details panel would close instead.
Assigned items weren’t copied when duplicating dependencies.
The dependency information wouldn’t display sprint information.
On dependencies, searching for a feature in the assigned items would return all features, not limited by the release programs or the depends on team program.
On dependencies, users couldn’t consistently focus on the Search field in the assigned items section.
On the program board’s quick view, the Stories section would display for external dependencies with no story associations.
When a dependency was opened from a a feature or story’s quick view and then closed, the dependency details panel would remain open and the quick view would close instead.
Creating a program increment with a blended rate and release funding wouldn’t display those fields in the audit log.
On forecasts, the estimation for the active program increment on epics and capabilitieswould display in the Previous estimates section when more than two earlier program increment associations were removed.
On the stories page, selecting the ? icon next to an acceptance criteria listed in the grid wouldn’t display rank information.
On the sprint slideout, the error message that displayed on sprints removed from a program increment didn’t contain a working redirect link to view the program increment slideout.
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 Version |
Continuous Track for Sandbox and Production (if elected) Environments |
Bundled Track for Production Environments |
On-Premise Environments |
|---|---|---|---|
|
11.17.0 Feature release |
October 10, 2025 | ||
|
11.17.1 Maintenance release |
October 24, 2025 | October 24, 2025 | November 12, 2025 |
|
11.18.0 Feature release |
November 14, 2025 Note: Release was delayed |
||
|
11.18.1 Maintenance release |
November 21, 2025 | November 21, 2025 | December 10, 2025 |
|
11.19.0 Feature release |
December 5, 2025 | ||
|
11.19.1 Maintenance release |
December 19, 2025 | December 19, 2025 | January 7, 2026 |
|
11.20.0 Feature release |
January 5, 2026 Note: Deployment occurred on a Monday due to winter holidays. |
||
|
11.20.1 Maintenance release |
January 16, 2026 | January 16, 2026 | February 4, 2026 |
|
11.21.0 Feature release |
January 30, 2026 | ||
| 11.21.1 Maintenance release |
February 13, 2026 | February 13, 2026 | March 4, 2026 |
| 11.22.0 Feature release |
February 27, 2026 | ||
| 11.22.1 Maintenance release |
March 13, 2026 | March 13, 2026 | April 1, 2026 |
| 11.23.0 Feature release |
March 27, 2026 | ||
| 11.23.1 Maintenance release |
April 10, 2026 | April 10, 2026 | April 29, 2026 |
| 11.24.0 Feature release |
April 24, 2026 | ||
| 11.24.1 Maintenance release |
May 8, 2026 | May 8, 2026 | May 27, 2026 |
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.21 was deployed to environments on the continuous release track on February 3, 2026. It will then be deployed to environments on the bundled release track on February 13, 2026. The following changes are included in version 11.21:
Enhancements and features:
Bug fixes delivered in 11.21:
| View name | Description |
| Dependency Work Item Relation |
|
| Link NPV Forecast Financials |
|
| Team Sprint Costing |
|
| Team Sprint Costing Allocation |
|
| Financial Snapshot Completed Features |
|
The 11.21 release of Enterprise Insights (EI) will not be deployed to environments on the continuous release track on January 30, 2026. We are postponing this deployment to ensure the release meets our high standards for quality. We expect to release this version to environments on the continuous release track on February 3, 2026. It will then be deployed to environments on the bundled release track on February 13, 2025.
Jira Align's Enterprise Insights (EI) version 11.20 was deployed to environments on the continuous release track on January 5, 2026. It will then be deployed to environments on the bundled release track on January 16, 2026.
This release aligns Enterprise Insights with Jira Align version 11.20 and includes the latest tested build, but does not introduce changes to existing data, views, or behavior.
The Enterprise Insights schema has been updated to version 11.20 with no changes to tables, columns, or data types.
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.
| EI Version |
Continuous Track for Sandbox Environments |
Bundled Track for Production Environments |
On-Premise Environments | Schema |
|---|---|---|---|---|
| 11.18 |
November 14, 2025 Note: Release was delayed |
November 21, 2025 | December 10, 2025 | Schema for 11.18 |
| 11.19 | December 5, 2025 | December 19, 2025 | January 7, 2026 | Schema for 11.19 |
| 11.20 | January 5, 2026 |
January 20, 2026 Note: Release was delayed |
February 4, 2026 | Schema for 11.20 |
| 11.21 |
February 3, 2026 Note: Release was delayed |
February 13, 2026 | March 4, 2026 | |
| 11.22 | February 27, 2026 | March 13, 2026 | April 1, 2026 | |
| 11.23 | March 27, 2026 | April 10, 2026 | April 29, 2026 |
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.
We are changing the data type of several columns in EI to assure:
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.
To prepare for the data type changes, you can take the following actions:
Use the table below to review the columns that will change from NCHAR to NVARCHAR.
| View name | Column names | Old data type | New data type |
|---|---|---|---|
| Anchor Sprint |
|
NCHAR(50) | NVARCHAR(50) |
| Epic |
|
NCHAR(50) | NVARCHAR(50) |
| Epic History |
|
NCHAR(50) | NVARCHAR(50) |
| Feature |
|
NCHAR(50) | NVARCHAR(50) |
| Feature History |
|
NCHAR(50) | NVARCHAR(50) |
| Jira State Mapping |
|
NCHAR(50) | NVARCHAR(50) |
| Jira State Object Mapping |
|
NCHAR(50) | NVARCHAR(50) |
| Program Increment |
|
NCHAR(10) | NVARCHAR(10) |
| Sprint |
|
NCHAR(50) | NVARCHAR(50) |
| Story |
|
NCHAR(50) | NVARCHAR(50) |
| Story History |
|
NCHAR(50) | NVARCHAR(50) |
| Task |
|
NCHAR(50) | NVARCHAR(50) |
| Theme |
|
NCHAR(50) | NVARCHAR(50) |
| Theme History |
|
NCHAR(50) | NVARCHAR(50) |
| Capability |
|
NCHAR(50) | NVARCHAR(50) |
| Capabiltiy History |
|
NCHAR(50) | NVARCHAR(50) |
| Region |
|
NCHAR(10) | NVARCHAR(10) |
You can subscribe to three Help Center sections to receive notifications the instant release note articles are published:
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!
Our mission at Jira Align is to Simplify Software at Scale by bringing your business and your software development organization together in one intuitive platform.
2025 © All Rights Reserved.
|
|
|
|