Release notes for 11.13.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: July 11, 2025 to include bug fixes delivered during the week

Coming soon

Upcoming end-of-support (EOS) status and removal for JET app

The JET app for Jira will be designated with end-of-support (EOS) status as of September 17, 2025. We then plan to remove access to the app sometime before December 31, 2025. We’ll provide updates on this timeline in future release notes. This removal is to support Atlassian’s EOS plan for marketplace apps built with Connect.

Enhancements and features

These features for 11.13 were released to environments on the continuous release track on June 20, 2025, in version 11.13.0. The features will be released to environments on the bundled release track on July 3, 2025, in version 11.13.1.

Smart links for Jira Align work items in other Atlassian apps

Introducing Jira Align smart links: your new way to effortlessly reference and preview Jira Align work items across Atlassian products. Paste a link to a Jira Align item and enjoy an instant, rich preview with key details like title, state, description, and owner, all within your workflow.

This feature supports themes, epics, capabilities, features, dependencies, risks, and objectives. Choose between inline and card views to suit your needs.

Notes: 

• To connect Smart Links from Jira Align, your instance must be mapped to an Atlassian organization. If you have not set up mapping before, contact Atlassian support for assistance.
• We are following a progressive rollout. If you don’t see Smart Links right away, don’t worry – it will be available for your instance soon as we expand access to all customers.

Beta roadmaps: Milestones

You can now view and manage milestones created on work items on beta roadmaps. To display milestones on a roadmap, switch on the Show milestones toggle inside the View settings menu.

When the setting is switched on, any milestones that have a set Due date will display with a diamond icon on a roadmap item’s bar. Hover over the icon to display details about the milestone in a card. You can select the Edit milestones button to open the item’s details panel, where you can add, edit, and remove milestones.

New ownership and notification options for dependencies

We’ve enhanced the dependency object by adding three new fields, giving you more ways to identify ownership on each side of a request, and keep others informed:

• Requester lets you indicate the individual responsible for the requesting side of a dependency, so the responding team knows who to reach out to for more discussion. This is useful for teams where the person creating the dependency may not be directly making a request.
• Owner provides a way to identify the individual responsible for responding to a dependency, or in some organizations, the team member who manages tracking of dependencies.
• Notify lets you send notifications to one or more Jira Align users. You can also include external entities; notifications will be directed to the designated Jira Align owner. Notifications will be sent to users in the Notify field when a dependency is created or updated.

Requester and Owner have also been added as options in the Columns Shown menu in dependency grid, as well as filter options.

New fields for tracking release vehicles

We’ve enhanced release vehicles by adding a Summary text area field to better track context on a release vehicle. This field supports the Atlassian Documentation Format, similar to the Description field for other Jira Align work items.

We have also added the release vehicle creation date to the page footer, as well as adding it as a column and filter option in the release vehicle grid to improve searching for release vehicles.

These features will be available in 11.13 for Cloud customers and in 11.14 for on-premise environments.

Removal of legacy objective tree and details panel

As previously announced, legacy objective experiences have been removed from Jira Align in version 11.13.X for cloud environments and will be removed in version 11.14.X for on-premise environments.

Removal of Enable Team Hierarchy setting

As mentioned in our previous release notes, we’re removing the platform setting controlling the new team hierarchy menu. Now, all users will have the new menu.

The new Teams menu simplifies five options down to one, allowing you to quickly access recent and saved contexts, and view how your portfolios, solutions, programs, and teams relate to each other, which helps you find teams within the context of other teams.

New Jira connector sprint mapping logic

Currently, the Jira connector maps the first integrated sprint based on the end date and all following sprints based on the order of the sprints on the Jira board. Teams in Jira Software have to follow specific practices to avoid sprint mapping issues, like not changing the order of the sprints on the board or not using “bucket/planning” sprints. At scale, this is hard to communicate and manage.

To help address these challenges, we’re introducing new logic and a new connector setting to map sprints based on sprint end dates only.

This logic still uses Jira sprint mapping buffer days to map a Jira sprint to a Jira Align anchor sprint, but will only map sprints if there is an end date on the Jira sprint. This allows for more flexibility in the way teams work in Jira. They can reorder sprints without impacting mappings, and they can use bucket/planning sprints as long as there isn't an end date on the Jira sprint.

Once you change the setting map sprints based on their end dates, the setting will be locked. We believe this new logic will significantly improve sprint mapping reliability and we encourage all to use it. No existing sprint mappings will be impacted when changing the logic.

In an upcoming release, we’ll be announcing the end of support of board order logic.

Rich text on status reports

We recently introduced the Atlassian editor on work items, and now we’re updating key reports to render rich text. Now, when using the status reports, you’ll see rich text instead of the raw data.

Deactivation of inactive connectors

We identified a number of Jira connectors meet one of the following two conditions:

1. In an inactive state, but have the background connector service running
2. Not connected to Jira

In this release, we’re going to uninstall the background service for these connectors. These connectors will still be accessible, and no connector settings or mappings will change. If you need to use this connector in the future, contact Support and they will reinstall the service.

Bug fixes

Last updated: July 11, 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. 

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

11.13.0

• Users could remove values from the the required fields on the Azure DevOps settings slide-out.
• The value for the Need by dependency field would display in the Blocked field.
• On the program increment progress report, when drilling down, misaligned stories weren't counted on the Burnup > View Theme charts.
• On the feature backlog, the primary program filter couldn't be removed when selecting the X icon.
• Extra records about additional program changes on epics, features, and capabilities would display in audit logs.
• Platform terminology changes to features weren't reflected in the risks relationship filter and Jira Settings > State Mapping.
• The indentation of discussion comments were inconsistent between newly added and older comments.
• Users without Add/Save objective system role permissions couldn't add work items to objectives.
• On status reports, the text in the Description column wasn't fully visible.
• A blank screen would display when viewing custom rooms from a link.
• Users couldn't filter by program increments in the strategy room.
• When creating a new theme, the themes grid wouldn't update until the page was refreshed.
• When importing capabilities, the conversion of TW estimates was incorrectly calculated.
• Identified and closed a vulnerability related to the recycle bin.
• Identified and closed a vulnerability related to team meetings.
• Identified and closed a vulnerability related to email logs.
• Identified and closed a vulnerability related to dependencies.
• Identified and closed a vulnerability related to success criteria.
• Identified and closed a vulnerability related to tasks.
• Identified and closed a vulnerability related to capabilities.
• Identified and closed a vulnerability related to sprints.
• Identified and closed a vulnerability related to the Azure DevOps connector.

11.13.0.0627

• On beta roadmaps, icons for some milestone start dates were displaying in the incorrect location.
• Identified and closed a vulnerability related to ideation.
• Identified and closed a vulnerability related to features.

11.13.0.0702

• On beta roadmaps, the start date milestone icon were displaying in the wrong location.
• Dependency notifications weren’t sent to some users.
• The Push to Jira timer on Jira connectors wouldn’t update while the sync was running.
• Identified and closed a vulnerability related to ideation.

11.13.0.0709

• The organizational hierarchy report wouldn't load large data sets.
• Identified and closed a vulnerability related to ideation.