Release notes for 11.12.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: June 13, 2025 to include bug fixes delivered during the week

Coming soon

Upcoming removal of legacy objective tree and details panel

With the launch of the OKR hub and the improved objective details panel, legacy objective experiences will be removed from Jira Align in version 11.13.X for cloud environments, and version 11.14.X for on-premise environments.

Note that both of these experiences are designated with end-of-support (EOS) status; we will no longer file new bugs until their removals.

Enhancements and features

These features for 11.12 were released to environments on the continuous release track on May 23, 2025, in version 11.12.0. The features will be released to environments on the bundled release track on June 6, 2025, in version 11.12.1.

Team hierarchy navigation menu enabled for all

As mentioned in our community roadmap article and in our previous release notes, we recently released a new team hierarchy selector in the top navigation bar to better visualize and navigate your team structure. The new Teams menu simplifies five options down to one, lets you quickly access recent and saved contexts, and see how your portfolios, solutions, programs, and teams relate to each other.

The Teams menu will be enabled by default for all environments with this release. To temporarily disable this menu, navigate to the General tab in Platform settings and select No in the Enable Team Hierarchy dropdown.

In the 11.13.X release, this setting will be permanently enabled for all users. We’re delaying this activation by one release cycle to ensure you have time to transition your teams to the new navigation flow.

 

Over the next few weeks, our Content Design team will be updating articles and guides with team hierarchy navigation information. Thank you for your patience as we work to make these changes!

Removal of Jira Align API tokens when Atlassian Guard is configured

We’ve removed existing Jira Align API tokens when you have Atlassian Guard set as your authentication method. If you use Atlassian Guard authentication and were using Jira Align API tokens, we recommend that you create Atlassian API tokens as soon as possible to prevent any disruptions with your integrations. Atlassian API tokens offer enhanced security features within Atlassian Guard such as auditing, revoking, and blocking of tokens.

Create Atlassian API tokens with scopes

When using Atlassian Guard as your authentication method, you can now create Atlassian API tokens with scopes. Scopes define the level of API access to data in Jira Align and other Atlassian apps. We recommend creating tokens with scopes as they provide more security options.

Jira Align supports the read and write scope options.

Explore hierarchies and share filtered links with beta roadmaps

We’ve added two new features to the beta roadmaps experience:

You can now explore the hierarchy of roadmap items, from themes all the way down to the feature level. Select the > icon next to a roadmap item to expand its hierarchy. When viewing an objective roadmap, the next level of hierarchy will be the work item type mapped to that objective tier in portfolio settings.

Use the new Share button in the upper-right to send someone the same view of the roadmaps page, with all of your navigation, column, and filter selections included. These improved links will let you set the correct context with others, when planning against a select set of filters or other criteria.

Note: Shared links will continue to follow system role and team permissions. If you don’t have access to a team or roadmap item, they won’t be visible from a shared link.

Check out beta roadmaps in production

We’re making the beta roadmaps experience optionally available in production environments beginning with version 11.12.1, which is scheduled for release on June 6, 2025. We’re accelerating this availability, as we’ve heard that you’d like to test the new experience with production data.

 

To activate beta roadmaps for your users, switch on the Roadmaps (New)system role toggle in one or more of the following hierarchies: Enterprise, Portfolio, Solution, and Program.

Note: If you have previously tested beta roadmaps in a sandbox environment, you will need to re-enable the page for system roles as of version 11.12.1. To ensure production systems did not have users with unexpected access, we ran a script to provide an opt-in experience for all sites.

The timeline for removing the current roadmaps page has not changed. Both experiences will be available for the next several months as we continue to collect feedback on the new version, add features, and make other usability improvements. We’ll wait until the new experience is out of beta and has been adopted by a majority of users before setting a removal date for the current page.

What’s next?

Our next set of enhancements will help you maintain critical data hygiene, by allowing inline editing of dates, and offering suggestions for empty date fields. These suggestions will initially use details from associated program increments to propose dates that keep your work and planning periods aligned. We’re looking at more ways to suggest dates based on other related data.

We’re also readying a better experience for viewing and managing milestones created on roadmap items. Like the current roadmap, milestones will need a due date in order to be visible, so ensure you’re setting date fields for milestones you’d like to work with on a roadmap.

New column on OKR hub

With the OKR hub rollout we have heard how the increased number of clicks to dive into key results details is slowing down OKR reviews, so we’ve added a new column to the hub that displays both key result titles and scores:

To enable the new column, select Key results from the Columns shown menu. After adding this column to the hub, you can rearrange its position in the grid and adjust its width according to your preference.

The column formerly known as Key results has been renamed to Key results count.

Reintroduction of Jira connector’s unassigned backlog sprint mapping logic

In a previous release, we announced new Jira connector sprint mapping functionality that improves on how Jira Align handles syncs when moving stories and defects to the unassigned sprint backlog. This enhancement was temporarily paused to account for situations where Jira statuses in various status categories were used. We’re happy to announce this feature has been enabled once again, with new logic to better sync items in various status categories.

When the Story sprint assignment sync direction Jira connector setting is Bidirectional:

• After moving a story or defect to the unassigned backlog in Jira Align, corresponding issues in Jira will be moved to the backlog.
• After closing a sprint in Jira, any open issues will have their corresponding stories or defects in Jira Align moved to the unassigned backlog. To determine if the issue is open, we check:
  • If Jira Status Category != Done, check additional fields for data.
    • If both Resolution and Resolution Date fields are empty, move the work item to the unassigned backlog in Jira Align.
    • If either Resolution or Resolution Date fields contain entries, do not move the work item in Jira Align.

When Story sprint assignment sync direction is set to Jira to Jira Align:

• After closing a sprint in Jira, any open issues will have their matching stories or defects in Jira Align moved to the unassigned backlog. The same logic listed in the section above is used to determine if the issue is open. 

These changes will be available in this version for cloud environments. On-premise environments will receive these changes in an upcoming release.

New APIs used with the Jira connector

In response to the upcoming Jira Cloud JQL endpoint removals, we’ve partnered with the Jira team to design and implement new endpoints in the Jira connector. These changes only impact backend connections to Jira Cloud, and you won’t notice any frontend changes.

Link Atlassian goals to Jira Align work items

In order to bring Jira Align closer to the Atlassian suite of apps, Atlassian Cloud users will soon be able to link Jira Align themes, epics, and capabilities to an Atlassian goal.

To support this upcoming feature, we’ve added a new section to details panels for themes, epics, and capabilities, titled Atlassian goals. Once a relationship has been defined between a Jira Align work item and an Atlassian goal, the linked goal will appear in the new section:

Linked goals will be displayed in a paginated table, featuring essential details such as the goal name, type, status, and owner. By selecting a goal, you can view its details in a new tab.

Removal of value engineering functionality

As previously announced, we’ve removed value engineering fields from work item details panels, as well as the value engineering report.

Embed Atlassian Analytics in external reports

You can now embed Atlassian Analytics dashboards inside Jira Align through the external reports page. This enhancement lets you avoid context switching between analyzing data from Enterprise Insights and managing items inside Jira Align. Simply paste the URL of the Atlassian Analytics dashboard into the iFrame URL field when creating a new external report.

Note: To embed Atlassian Analytics reports, you must enable Atlassian Guard authentication.

Bug fixes

Last updated: June 13, 2025 to 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. 

Internally-found issues

We’ve corrected the following bugs that were discovered while investigating related issues, building new enhancements, and performing maintenance:

11.12.0

• While mapping Jira projects to Jira Align programs in Jira connector settings, errors would display when using Firefox.
• The Confluence logo would display as misaligned after adding a Smart Link to a work item.
• The Burn Details panel on the program increment progress report did not include teams from additional portfolios or solutions set in extra configs.
• Reports would not display when using the My View setting in the team room.
• Initials inside default profile images were difficult to read when viewing the people page.
• Recently added defects would not display inside of story details panels.
• Sorting by program increment ID would cause an error on the program increments page.
• Child objectives were incorrectly associated with solution objectives in solutions that did not have capabilities enabled.
• Dependency audit logs did not contain records of setting Blocked fields to Yes.
• Dependency audit logs did not contain records of removing a program increment.
• Dependency audit logs did not contain records of edits to the Committed by field for multi-program dependencies associated with features.
• Identified and closed a vulnerability related to dependencies.
• Identified and closed a vulnerability related to note fields.
• Identified and closed a vulnerability related to status reports.

11.12.0.0528

• Themes were not correctly filtered by program increment on the strategy room.
• The character limit inside the Email CC field for enhancement group email settings was set to 100 instead of 1000.

11.12.0.0529

• Users without proper team permissions could see all capabilities from the kanban state view of capability backlogs.
• The Team filter on the work in progress by state report was not loading any values.

11.12.1.0612

• Solution teams would display in the search and the Recent and Saved tabs of the Teams selector when the Enable Solution Menu platform setting was disabled.
• The sidebar wouldn't display on solution-level pages when the Enable Solution Menu platform setting was disabled.