Release notes for 11.15.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: August 29, 2025 to update the list of 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.15 were released to environments on the continuous release track on August 18, 2025, in version 11.15.0. The features will be released to environments on the bundled release track on August 29, 2025, in version 11.15.1.

Updated filtering behavior for kanban teams in team room

As part of resolving JIRAALIGN-4043, we've made an update to the section header names when filtering Kanban team data in the team room. Previously, when searching for a specific work item or applying a state filter, results would display in the wrong week section.

Now, filter results will display in a new section, named Filtered results.

Objectives: Date platform terminology displayed in details panels

We improved the objective details panel to use platform terminology for date field labels: Start / Initiation and Target Completion. This unites the roadmap date column titles and the objective field labels to match.

Objectives: Improved save experience in details panels

We received feedback that some users found the objective summary field unintuitive as a required field, preventing users from successfully creating an objective. To address this, we have added a Summary field label, defaulted the cursor placement in that field, and included a ‘required’ label to emphasize that this field must be completed to create or save the objective.

Beta roadmaps: Sort by global rank

Need to view roadmap items by their overall importance? From the View settings menu, select the new Global rank option in the Sort by menu to put the highest-ranked items at the top.

Items will be sorted by their global rank, outside of any portfolio, solution, program, or program increment ranking. To view global rank:

1. Select Enterprise from the Teams menu in the top navigation bar.
2. From the sidebar, ensure no program increments are selected in the Program Increment dropdown.
3. Navigate to the backlog page. 

We're working on additional enhancements to this feature, including sorting by other ranking structures.

Beta roadmaps: View additional fields

We’ve also added the following fields to the Columns menu of beta roadmaps:

• Release vehicle

• Children*

• Story points

*Note: The Children column displays the total number of associated child work items, but your roadmap will only display items that meet navigation criteria, filter settings, and user permissions. For example, you may see 5 children listed for an epic, but expanding the hierarchy only displays 2 features, as those were associated with the program the roadmap is filtered to. This column behavior matches the legacy roadmap experience.

Over the next few releases, we’ll be adding more fields available to display, as well as expanding sort by and filtering options.

Audit log archiving

As announced in the previous release notes, we’re archiving all audit log entries that are more than 13 months old. This change will significantly improve the performance of audit logs and other pages inside Jira Align, especially in environments with large amounts of data. While these older audit log entries may not be visible in the UI or API, we will retain these records in our database tables, which you can access through Enterprise Insights.

Does this impact Jira Align’s data retention policy?

No. All audit entries, including those older than 13 months, will still be retained. They are moving to a new database table and will no longer be accessible in-product or through the APIs. Review our data retention policy for more details.

Can I use the /auditlog API endpoint to query time periods of more than 13 months in the past?

Our APIs will not return errors if you query time periods exceeding 13 months in the past, but the audit log entries will not be retrieved.

How do I get access to Enterprise Insights?

Contact your Atlassian sales team member to find out how you can get Enterprise Insights.

Jira connector: Immediate sync of newly integrated boards

To speed up the onboarding of new Jira teams and reduce administrative overhead, newly integrated Jira boards are synced immediately. Users will not need to wait at least an hour for the board timer to run before validating sprint mappings and syncing the team’s issues.

Azure DevOps connector: Support for Entra ID OAuth authentication method

Jira Align now supports the new, recommended Microsoft Entra ID OAuth method for integrating with Azure DevOps, which provides enhanced security and enterprise integration capabilities. You’ll see this new method as OAuth - Microsoft Entra in the authentication method dropdown.

With the rollout of Entra ID OAuth, Microsoft is no longer supporting its existing OAuth platform (OAuth - AzureDevOps in the authentication method dropdown). They will be announcing an end-of-life date in 2025.

Along with this change, we removed the previously deprecated NTLM authentication method from the dropdown.

Bug fixes

Last updated: August 29, 2025 to update the list of 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.15.0

• On the beta roadmaps, the portfolio and solution filters were tied to the singular version of platform terminology.

• Newly created work items wouldn’t display when searching for them in the top navigation bar.

• Email notifications weren’t sent when tagging a user in a discussion.

• On the objective details panel, dropdown custom fields would disappear if a deleted or invalid value was selected.

• Updating a solution’s portfolio through the API wouldn’t update the child programs.

• Key results would display on an objective’s details panel after the key result had been deleted.

• In epic and capability audit logs, changes to MVP values would incorrectly display as changes to the MMF field.

• When opening acceptance criteria in a feature’s Trace report, an error message would incorrectly display.

• When quick adding a story from the feature detail’s panel, the selectable story point options were Fibonacci values, even if Power of 2 was selected in portfolio specific configuration.

• Fixed capitalization and terminology issues in audit log messages for moving stories to the unassigned backlog.

• Audit log entries were missing when epics were copied with their children.

• Test Categories field updates weren’t captured in audit logs.

• On the beta roadmaps, the count of applied filters wouldn’t display when the browser zoom was 100%.

• On the beta roadmaps, switching between objective views, applying filters, and sorting columns would reset the selected time range.

• Copying capabilities with the API wouldn’t copy custom field values.

• Fixed several instances where finance platform terminology values weren’t respected.

• When a dependency’s Blocked value was set to No, the Blocked Reason field value wasn’t removed.

• When filtering the dependencies grid by multiple portfolios or solutions, only dependencies related to all portfolios/solutions in the applied filters would display.

• Users couldn’t create capabilities from the epic details panel when their system role permission to add capabilities was turned on and the permission to save capabilities was turned off.

• When users had permission to add and save capabilities and epics, the More Actions option wouldn’t display on the epics page.

• Selecting a capability’s parent epic link would cause several visual issues on the capability details panel.

• The Jira connector would incorrectly set Estimate T-shirt and Man Weeks to 0 for features when syncing Jira epics that didn't have those fields set.

• Kanban board descriptions could be longer than 100 characters.

• Users couldn’t save their timezone in their personal settings.

• When setting system role permissions, switching on child toggles in the Reports section wouldn’t switch on the parent toggle.

• Identified and closed a vulnerability related to the API.

• Identified and closed a vulnerability related to features.

11.15.0.0820

• On roadmaps, filtering features by release vehicle wouldn't work if the release vehicle wasn't assigned to any features.

11.15.0.0821

• When a program had been selected on a team objective and users wanted to reassign the program, the already-selected program would display in the search results.

11.15.0.0822

• On the beta roadmaps, an error would display when switching to the objective with the Global rank option applied.