Release notes for 11.11.X

Note: This article has been republished. This method is used to provide notification emails to users subscribed to feature release note updates. This article has been updated to provide a new timeline for the removal of value engineering, originally scheduled for release in this version.

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: May 16, 2025 to include include bug fixes delivered during the week

Coming soon

End-of-support status and upcoming removal of legacy objective details panel

With the launch of the improved objective details panel, the legacy objective details panel has been designated with end-of-support (EOS) status. While the page will remain available until version 11.13 for cloud environments and 11.14 for on-premise environments, we will no longer file or fix non-critical defects, focusing our development efforts on the new experience.

Future availability of Jira Align API tokens when Atlassian Guard is configured

In version 11.12.X, 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.

Removal of value engineering functionality in 11.12

In version 11.12, 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.12 to archive your data. You can use screenshots and Save options from your browser to capture the contents of a page.

Enhancements and features

These features for 11.11 were released to environments on the continuous release track on April 25, 2025, in version 11.11.0. The features will be released to environments on the bundled release track on May 9, 2025, in version 11.11.1.

Test out the beta roadmaps experience

We’re excited to introduce a beta version of our new roadmaps experience, designed to enhance your planning and tracking capabilities. This beta is currently available exclusively in sandbox environments on the continuous release track, allowing you to explore its features in a safe setting.

 

Testing in your sandbox

• To enable the beta version, switch on the Roadmaps (New) system role toggle in one or more of the following hierarchies: Enterprise, Portfolio, Solution, and Program.
• The beta experience is only available in sandbox environments for the next few months as we continue collecting feedback and adding functionality. 

In this beta, you can explore features like:

• A familiar, Jira-like interface for navigation and controls.

• Seamlessly move across work item types, now including program, solution, and portfolio-level objectives, providing a comprehensive overview of your strategic goals.

• Control the display of multiple roadmap item attributes in a consolidated Fields section.

• A simplified pattern for displaying progress bars for each roadmap item, using start and end date fields for work items and objectives to determine boundaries.

• Quick access to change your time scale to weeks, months, or quarters.

• Show labels for multiple program increments associated with your enterprise, portfolio, or solution, with the ability to quickly edit PI details and see time boundaries in relation to items on the page.

Improved objective details panel enabled for all customers

We’ve set the improved objective details panel as the default for all customers as the main place for creating and viewing objectives. This includes:

• A streamlined creation flow

• The ability to assign a theme to a portfolio objective

• Information sectioned into logical groups for quick location

• Clear roll-up of work items that contribute to overall progress

• The ability to access the legacy objectives tree page

As previously announced, the legacy objective details panel will be removed in version 11.13.

Learn more about the benefits and launch of the improved objective details panel on the Atlassian Community.

Opt-in to team hierarchy navigation

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

To turn on the team hierarchy navigation experience for your Jira Align instance, navigate to Platform settings > General tab and select Yes in the Enable Team Hierarchy dropdown.

In version 11.12, this setting will be permanently enabled for all customers. The legacy experience will be removed in version 11.14.

Atlassian editor on themes, epics, and capabilities

In a previous release, we added the Atlassian editor to features. This editor provides enhanced formatting capabilities like tables, code blocks, info panels, and more. Now, we’re adding the editor to capabilities, epics, and themes.

All themes will have this editor. If you have a Microsoft Azure DevOps connector, this editor will not be available on capabilities on epics. If you do not have a Microsoft Azure DevOps connector, this editor will be available on newly created capabilities and epics.

Smart Links are here!

We continue working to bring Jira Align onto to the Atlassian platform, providing familiar, consistent experiences across our apps. With our latest change, you can now see links to Atlassian pages and work items render as Smart Links inside Description fields for themes, epics, capabilities, and features. To enable this capability, you will need to enable Atlassian Guard as your authentication method.

When a Smart Link renders, you can use both the inline and card views.

Change to average process flow cycle time calculation

As part of investigating reporting bugs, we discovered that the calculation at the bottom of the process step cycle time chart did not align with expectations of how long items spend within a specified process flow.

Previously, the Average time in process flow value displayed at the bottom of the chart included all items assigned to any step in the flow. We’ve adjusted the calculation to only include items in the final step, indicating completion. The new calculation considers the total number of days all completed items spent in the process flow, and divides that by the number of completed items. This approach offers an accurate representation of the average duration items take to proceed through the flow, also known as cycle time.

We’ve also renamed this value to Average cycle time to better signal its purpose.

Atlassian Analytics info added to Enterprise Insights settings

With the launch of the Strategy Collection, Enterprise Insights (EI) is now easier to connect to Atlassian Analytics. We’ve added some notices about this connection and links to setup documentation inside the EI admin settings pages. EI settings pages are intended for connecting your data to a third-party business intelligence tool, while connections to Atlassian Analytics are done within that app. If your admins are looking to connect data to Atlassian Analytics, these messages will send them to the correct resources.

Bug fixes

Last updated: May 16, 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. 

Internally-found issues

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

11.11.0

• Jira Align pages that were removed were available to be added to checklists.
• On the process flow cycle time report, the average time in process flow was calculated incorrectly.
• On the release vehicle roadmap report, the list of release vehicles in the Extra Configs filter wasn't limited to release vehicles for a selected contributing program.

• The Daily Attendance section would display on the sprint coaching report, even though the daily attendance report was removed.

• After changing a feature's associated theme through import, when filtering the features page by the original theme, the feature would erroneously display in the filtered list.
• Changes to a theme's theme group assignment weren't displayed in audit logs.
• On the release vehicle roadmap report, a message specifying that no release vehicles were associated with the current PI would erroneously display when a release vehicle was assigned to the release but a contributing program wasn't selected for the release vehicle.
• On the people page, the text inside users' placeholder avatars would display as dark blue, causing contrast issues when the avatar's background was a dark color.
• The values for risk fields would be removed when updating the risk using the API.
• When adding a defect to a story through the story's details panel, the newly-created defect wouldn't display in the list of associated defects.
• When the Portfolio Ask field was marked as required for epics in details panel settings, the field wouldn't display as required on the epic's details panel.
• Identified and closed a vulnerability related to epics.
• The team details report wouldn't display when accessing the report through the program increment allocation report.
• Sorting the program increments grid by program increment would result in a "Whoops" error.
• Identified and closed a vulnerability related to creating features.
• Identified and closed a vulnerability related to the Jira Align backend.
• Identified and closed a vulnerability related to program increments.
• Identified and closed a vulnerability related to creating stories.
• Identified and closed a vulnerability related to editing sprints.

11.11.0.0426

• Identified and closed a vulnerability related to epics and themes.
• Identified and closed a vulnerability related to objectives.

11.11.0.0501

• Identified and closed a vulnerability related to capabilities.
• Identified and closed a vulnerability related to features.

11.11.0.0507

• The name of the Portfolio dropdown on the updated objective details panel displayed incorrect terminology.
• On the feature details panel, the Start/Initiation Date field would display a tooltip describing the Target Completion Date field.

11.11.1

• Identified and closed a vulnerability related to objectives.

11.11.1.0514

• Identified and closed a vulnerability related to link maps.

11.11.1.0515

• Identified and closed a vulnerability related to status reports.