Release notes for 11.18.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Coming soon

GA of beta roadmaps and removal of legacy roadmaps in 11.19

We are excited to announce that the beta roadmaps experience will move to general availability (GA) status next month. We’ll make new roadmaps experience the default, and remove the legacy experience in version 11.19.0, scheduled to begin deployments on December 5, 2025.

Review our community announcement for details on the transition, and further planned enhancements as part of GA.

Upcoming removal of JET app

The JET app for Jira reached end-of-support (EOS) status on September 17, 2025. We 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. For more information on how to track your Jira health, check our our article in the Atlassian Community.

New Recycle Bin and Delete APIs coming in 11.19 and 11.20

In the 11.19 and 11.20 releases, we plan to introduce a set of work item APIs that support both the recycle bin and deletion. A community article on how to prepare for these new APIs will be published next week. If you have any questions or encounter issues using existing experimental APIs, please reach out to Atlassian Support.

Enhancements and features

These features for 11.18 were released to environments on the continuous release track on November 14, 2025, in version 11.18.0. The features will be released to environments on the bundled release track on November 21, 2025, in version 11.18.1.

Beta roadmaps: New fields and filters

We’ve further expanded the beta roadmaps experience to help you find and organize work more easily. In this version, we’ve added the following fields for column views, along with more filtering options:

New columns

• Custom fields (text, single select, multi-select)
• Execution Team for features
• Product for features
• Estimate Points for features

Updated columns

• Blocked
  • Blocked fields now indicate the impacts of blocked child features. For themes, epics, and capabilities, the blocked field will change when any associated feature is blocked. The column also displays a count of blocked child features.
    
• ID and name
  • Expand icons > will no longer display for roadmap items that do not have any associated children.

Filters

• Execution Team for features
• Product for features

Beta roadmaps: New group by options

You can now group roadmap items by state, primary program, and for features, execution team. Use this option to identify groups of items that need intervention, apply to a specific program, or are handled by a specific team.

Beta roadmaps: Additional state colors

Thanks for your feedback requesting better visual separation of roadmap item states and statuses. We’ve added more colors to roadmap item bars when coloring by state. This update provides better clarity between similar states, so you know exactly where a roadmap item stands with a quick glance.

Beta roadmaps: Export as PNG

Use the new export to PNG option, found in the top-right corner of the page, to quickly gather an image of your customized roadmap view.

The export is capable of displaying a maximum of 500 items.

Note that if a roadmap view contains no items, the export option will be disabled.

Jira connector: Automatically assign features to a Jira project

Now, when mapping Jira projects to Jira Align programs in Jira connector settings, you can specify whether the Jira project should be enforced as the only option to assign the feature to, or whether the Jira project should be automatically assigned to the feature.

We commonly see organizations using shared “program” level Jira projects alongside specific team-level Jira projects. A setup like this provides teams with visibility into their work, while also allowing multiple teams to contribute to the work. However, we often see the wrong Jira project being selected for features in Jira Align, or the Jira project missing altogether. This leads to manual clean-up efforts, a lack of visibility into the team's priorities, and a lack of visibility into team workloads.

With the Enforced Jira Project setting now available in Jira connector project configurations, we’ve also updated the behavior of the Jira project field on feature details panels.

To set a Jira project as enforced, navigate to Jira Settings > Manage Projects and select the project key you want to update. Switch on the Enforced Jira Project setting.

If the Jira Project field is required in your Jira Align portfolio’s details panels settings, we’ll automatically assign newly created features to the mapped Jira project.

If the Jira Project field is not required in Align, the enforced Jira project will be the only option in the Jira project dropdown. This logic applies to all create and update methods, whether that is the standard new item details panel, quick add, import, APIs, or other methods.

Jira connector: APIs to map Jira status and Jira Align states/steps

To simplify and speed the onboarding of new Jira teams to Jira Align, as well as simplify ongoing maintenance of the connector, you can now use APIs to map Jira statuses and Align states/steps.

Smartlinks supported in Slack

You can now view Jira Align smartlinks directly in your Slack channels and DMs, making it easier to share and preview work items without leaving your conversations.

To turn on this functionality, you'll need to reinstall the Jira Cloud for Slack app. See Slack’s documentation for more details.

Smartlinks in Slack are only available if your Jira Align site is connected to Atlassian Identity. If your organization has not yet established this connection, please contact Atlassian Support to enable Atlassian Identity for your Jira Align instance.

Azure DevOps connector: Configuration and sync logs in EI

The Azure DevOps connector sync and configuration logs are now available in Enterprise Insights, enabling customers to create custom reports to monitor connector activity and identify issues in near real-time.

In an upcoming release, we’ll be adding the Azure DevOps queue logs to Enterprise Insights.

Bug fixes

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.18.0

• When grouping features by owner on the beta roadmaps page, newly unassigned features were not displayed in the unassigned section.
• When opening a shared beta roadmaps link with missing permissions, a 500 server error was displayed.
• When searching by program on a kanban board for capabilities, no results would display.
• Some users could view epics and capabilities on backlog pages for programs they were not members of.
• When performing a mass add of dependencies to a kanban board, dependencies were not moved to columns.
• When moving items on a kanban board backlog view, counts were not updated.

11.18.0.1115

• A "Whoops" error would display when filtering kanban boards by tags.