Release notes for 11.14.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: August 8, 2025 to update the list of bug fixes delivered during the week, and include the mention of a display change for user icons in team details panels

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.

On-premise environments: Test script required when upgrading to 11.13 or higher

As of version 11.13, the Jira connector has been upgraded to use the .NET8 runtime. Due to HTTP stack changes in .NET8, we are providing a test script to verify that your Jira connector can reach Jira. You should run this test prior to updating your on-premise environment to version 11.13 or above for the first time.

Review the latest entry inside the JiraAlign Upgrade Notes.txt file in the 11.13 download package for instructions on how to run the test script, and what to do next based on the results. Downloads of 11.13 will be available on Wednesday, July 23, 2025.

Enhancements and features

These features for 11.14 were released to environments on the continuous release track on July 18, 2025, in version 11.14.0. The features will be released to environments on the bundled release track on August 1, 2025, in version 11.14.1.

Beta roadmaps: Inline date edits

Note: To ensure optimal performance and quality, this feature was activated for sandbox environments on Tuesday, July 22, 2025.

You can now make quick edits to beginning and ending date fields on the beta roadmaps page. To edit dates on a roadmap, set the Start / Initiation and/or Target Completion fields to display from the Columns menu, then select a roadmap item’s date to open a calendar picker. 

Your selection will be saved instantly, once you leave the field.

Notes:

• Date fields may be named differently in your instance according to custom terminology settings.
• Ending dates must be equal to or later than beginning dates.

Beta roadmaps: Suggested dates

Note: To ensure optimal performance and quality, this feature was activated for sandbox environments on Tuesday, July 22, 2025.

Need some help finding the right entries for empty date fields? Easily fill in missing dates on your roadmap with the new suggested dates feature. To get started, select the Suggested dates button at the top of the page: 

This places you into suggested dates mode, where suggestions display in italics with a plus icon. Striped roadmap item bars are also shown, giving you a visual cue on your timeline. 

Dates are suggested using a roadmap item’s program increments. The start date of the earliest program increment is referenced for blank beginning date fields, and the end date of the latest associated program increment is used for blank ending date fields. 

To use a suggestion, select a cell, and a calendar picker will display with the recommended date highlighted. Select the date to stage the change as an edit to the roadmap item. You can also select a different date. 

The cell will display with a blue highlight in its top-right corner, indicating it is a pending change. After you’ve staged one or more date edits, select the Submit button at the top of the page. 

Select Confirm to save your changes. 

Any suggestions you did not interact with will be ignored, and you can return to suggested dates mode to see them again.

Beta roadmaps: Track progress

Now, you can easily monitor the status of roadmap items as work moves forward, helping you anticipate issues and make timely adjustments. 

To see status at a glance, add the Progress column to your roadmap from the Columns menu. A mini progress bar will display for each roadmap item. The bar will show as filled, depending on the percentage of aligned work.

For objectives, the bar will fill according to completed key results. For work items, the bar will fill using either accepted story points or count of child work items, depending on the Progress bar status dropdown found inside portfolio settings: 

Select any progress bar to see a detailed card, showing more data about the item's progress.

Specific add and save permissions for epics and capabilities

Note: To ensure optimal performance and quality, this feature was activated for sandbox environments on Thursday, July 24, 2025.

We're introducing separate Add and Save system role permission toggles for epics and capabilities, giving admins more precise control over who can create versus edit high-level work items. Previously, a single toggle governed both actions, making it difficult to restrict creation without also blocking edits. The new options provide more consistency in Jira Align, matching the permissions model for themes, features, and stories.

The save permission controls the ability to edit epics and capabilities; this affects all types of saved changes, including inline edits made to health and status attributes on pages like status reports and roadmaps. 

You can review the new permissions on the far-right side of the rows for epics and capabilities: 

Existing permissions have been migrated so that your users retain current access without interruption. Any user or role that had the old Add/Save permission toggle enabled will have both the new add and save toggles enabled.

Corrected permissions for copying features

As part of our work to provide more consistency with new add and save permissions, we were able to identify and resolve a bug related to features. Previously, the Save permission was required in order to use the Copy function on a feature's details panel. We've updated system logic to validate the correct permission toggle, Add, as a copying creates a new work item.

Jira connector fixes with continuous deployments

Continuous deployments, which allow for quicker resolution and deployment of bug fixes throughout the week, now include changes to the Jira connector. This means that bugs related to the connector can be fixed as soon as a resolution is available, instead of waiting for the next Friday maintenance release window.

New banners in audit logs

To prepare for the upcoming archival of older audit log entries, we've added informational banners to the following pages in Jira Align:

• Main audit log
• Jira connector audit logs
• Work item audit logs
• Feature audit logs accessed from the program board

As previously announced in our product roadmap presentation, we plan to begin archiving audit log entries greater 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. 

We plan to roll out these changes using a phased approach. We'll provide more details and what versions we are targeting for release in the coming weeks.

Faster loading of user icons in team details panels

Note: This enhancement was deployed to sandbox and production environments on Friday, August 8, 2025.

As part of resolving reports of slow load times inside team details panels, we've changed the display of each user in the Members tab from the uploaded profile image to the default initials icon. This change will result in significantly faster loading times for team panels, especially those with large amounts of members.

You can view more details about a user, including their profile image, by hovering over their icon. 

Bug fixes

Last updated: August 8, 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.14.0

• On beta roadmaps, date information displayed when hovering overlapped displayed column data.
• On the drill-down view of the program increment progress report, predicted, pessimistic, optimistic lines were not displaying for themes.
• On the program tracking report, the wrong state was displayed when viewing a tool tip for escalations.
• From the program increment progress report, the burn details panel would show a duplicate record inside the End Date column.
• The blank state message found on the status reports page contained a spelling error.
• Audit logs for objectives were not showing changes to scores after adding a key result without baseline or goal values.
• The Tier field on objectives was not displaying correctly when users with view only permissions accessed details panels.
• When adding or removing items from objectives, the Key results and Aligned work items sections of details panels were not updating.
• Unexpected special characters were displayed in audit log entries after modifying an epic's relationship.
• A blank details panel would display when attempting to edit an epic’s process step.
• Team details panels were not rendering correctly when a team was associated with a program with a lengthy name.
• Child items would not reassign correctly after splitting an epic with capabilities enabled.
• Users without edit permissions to features were able to edit acceptance criteria, but unable to save.
• On epic and capability backlogs, the MVP filter was incorrectly displayed as MMF.
• On backlogs, the total items count would not change after moving a theme to another release or the unassigned backlog.
• Custom terminology settings were not respected when viewing discussions for features.
• On the epics grid page, an error would display when attempting to access the Print epic cards option.
• On epic and capability backlogs, an error would display when attempting to drag and drop cards inside kanban views.

11.14.0.0719

• Identified and closed a vulnerability related to updating health.

11.14.0.0724

• The Mass add or remove option was not functioning correctly on kanban boards.

11.14.1.0806

• On-premise backoffice service would not load due to a missing configuration setting.

11.14.1.0808

• Some users experienced slow load times on program, portfolio, and solution team details panels.
• Identified and closed a vulnerability related to API token validation.