The Atlassian Jira Align team is pleased to announce Jira Align v.11.10.
Last updated: April 11, 2025 to include include bug fixes delivered during the week
Coming soon
Removal of value engineering functionality in 11.11
In version 11.11, we’ll remove value engineering functionality from Jira Align. This includes both the value engineering fields found in the Value tab of work item details panels and the value engineering report. These functions were previously designated as end-of-support status, and we’re ready to remove them from the app.
If you have used this functionality in the past and would like to make a record of your entries, please visit the value engineering report prior to version 11.11 to archive your data. You can use screenshots and Save options from your browser to capture the contents of a page.
Future availability of Jira Align API tokens when Atlassian Guard is configured
In version 11.12, we plan on deprecating the Jira Align API tokens when you have configured Atlassian Guard as the authentication method with Jira Align. If you have enabled Atlassian Guard authentication and are using Jira Align API tokens, we recommend that you switch to Atlassian API tokens as soon as you can to prevent any disruptions with your integrations. The Atlassian API tokens offer enhanced security features within Atlassian Guard such as auditing, revoking, and blocking of API tokens.
Q1 2025 roadmap presentation
Check out what we're currently working on in our latest quarterly roadmap presentation. This quarter, we're delivering an async review on the Atlassian Community as we focus on preparations for Team '25. We expect to return to live roadmap calls later this year.
Enhancements and features
These features for 11.10 were released to environments on the continuous release track on March 28, 2025, in version 11.10.0. The features will be released to environments on the bundled release track on April 11, 2025, in version 11.10.1.
Update on reintroduction of Jira connector sprint sync logic
We have paused the activation of the Jira connector sprint changes previously announced in 11.9.X release notes, as we investigate some reports of unexpected sprint assignment changes in Jira Align.
We are planning to reactivate the feature in a future release with additional changes that will account for the unexpected behavior. Review our full announcement for details on how this uncommon issue can occur, and steps you can take to see if you're affected.
OKR hub enabled for all environments
We’ve enabled the OKR hub for all environments as the main place for managing and tracking objectives. This includes:
- The sidebar menu option has been renamed from Objectives tree to OKR hub.
- Users will land in the hub with the correct tier, team, and program increment selected in page filters, depending on navigation and sidebar selections.
- A spotlight tour on first visit to refresh how the Tier filter works, and how to access the legacy objectives tree page.
As previously announced, the legacy objectives tree page will be removed in version 11.13.
Review our post on the Atlassian Community for more about the benefits and launch of the OKR hub.
End-of-support status for legacy objectives tree
With the launch of the OKR hub, the legacy objectives tree page has been designated with end-of-support (EOS) status. While the page will remain available until version 11.13, we will no longer file or fix non-critical defects, focusing our development efforts on the new experience.
Removal of legacy pages
As previously communicated, we’ve removed the following pages from Jira Align:
- Admin task status page
- Standup attendance report
Bug fixes
Last updated: April 11, 2025 to include 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.
Key | Summary | Release Version |
JIRAALIGN-5927 | Import- edit features via import corrupts Theme's assignment | 11.10.0 |
JIRAALIGN-5984 | Feature Recycle/Cancel bin: any user with access to the bin can see all the items on it | 11.10.0 |
JIRAALIGN-6219 | Ideation Portal - Filter for external users is empty | 11.10.0 |
JIRAALIGN-6849 | Objectives - Unable To Edit Objective If The Assigned Theme Is Deleted | 11.10.0 |
JIRAALIGN-7588 | Sprint Capacity Report : Old sprints (that ran in the past but are not closed) will not show the 'Remaining allocation' as 0, but show a full one same as 'Member Allocation' currently | 11.10.0 |
JIRAALIGN-7919 | Epics/Capabilities Recycle/Cancel bin: any user with access to the bin can see all the items on it | 11.10.0 |
JIRAALIGN-7932 | Jira Align API - Can't create Story with Jira Project set | 11.10.0 |
JIRAALIGN-7962 | Add Epic: The fields Strategic Diver and the Investment Type are not recorded in the audit log when adding an Epic | 11.10.0 |
JIRAALIGN-7976 | Release Vehicle Roadmap report displays RVs outside the selected scope | 11.10.0 |
JIRAALIGN-8059 | Date Created column for Themes in Enterprise Insights is not being updated | 11.10.0 |
JIRAALIGN-8064 | When updating the Jira Timers under Jira Settings > Jira Setup, the values are saved, but they revert after the first run | 11.10.0 |
Internally-found issues
We’ve corrected the following bugs that were discovered while investigating related issues, building new enhancements, and performing maintenance:
11.10.0
- Exports of defects would not complete.
- When viewing the forecast page, incorrect work item terminology was displayed for epics when hovering on the Progress column.
- Users without the correct system role permissions were able to access the epic status report.
- When viewing the features grid page, the top navigation bar would disappear when sorting a column with pagination.
- Identified and closed vulnerabilities related to objective details panels.
- Identified and closed vulnerabilities related to creating risks.
11.10.0.0403
- Errors would display when navigating to a program using the sidebar.
11.10.0.0408
- Release vehicle Health fields would not save changes in details panels when using Google Chrome web browser.
- Messaging displayed on the release vehicle roadmap when no release vehicles were found in the selected team hierarchy was incorrect.
- Identified and closed vulnerabilities related to story details panels.
Join the Atlassian Community!
The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.
Need to contact Jira Align Support? Please open a support request.