Release notes for 11.9.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 custom room filters, originally scheduled for release in version 11.9.

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: March 28, 2025 to include details of a previously unreported feature. 

Coming soon

Removal of standup attendance report in 11.10

In version 11.10, we’ll remove the standup attendance report from Jira Align. We’re removing this report as it was tied to legacy functionality, standup meetings, which was removed in version 11.5.

If you have used this functionality in the past and would like to make a record of your entries, please visit these pages prior to version 11.10 to archive your data. You can use screenshots and Save options from your browser to capture the contents of a page.

Update on OKR hub enablement

To update our previous announcement, we'll be delaying the OKR hub rollout to version 11.10 to include a critical improvement in the alignment of the sidebar navigation filters with OKR hub filters.

In version 11.10, the sidebar navigation link will be renamed from Objectives tree to OKR hub. Selecting OKR hub will land users in the OKR hub with the sidebar tier, team, and program increment selections applied to the OKR hub page filters.

We welcome feedback on the OKR hub as we roll out the transition from the legacy objectives tree.

Objective details panel improvements

In an upcoming release, we’ll be rolling out improvements to the new objective details panel to all customers, not just customers who have the feature toggle enabled. These improvements include a streamlined creation experience, clear information architecture, and more flexibility assigning work items from other portfolios. By version 11.13, the legacy objective details panel view will be removed and fully replaced by the new and improved objective details panel.

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

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

Note: Atlassian API tokens now follow a 1-year expiration policy.

Enhancements and features

These features for 11.9 were released to environments on the continuous release track on February 28, 2025, in version 11.9.0. The features will be released to environments on the bundled release track on March 15, 2025, in version 11.9.1.

New location for Theme field in objective details panels

While fixing a bug for themes assigned to portfolio objectives, we made the decision to move the Theme field to the right side of the objective details panel. We made this change as theme is dependent on related fields in the new location, and needs to be saved through the Save button in the top-right. This fix will ensure the state of the objective is correctly saved and maintained.

Reintroduction of Jira connector sprint sync logic

As previously announced, we’re reintroducing an enhancement to Jira connector sprint assignment logic. With this version, you can control how sprint assignments are synced for both stories and defects through the story sprint assignment sync direction setting.

Review our full announcement for details on how to use this setting during normal operations, and how to modify the setting when deleting sprints in Jira Align as part of correcting sprint misalignments.

Jira Align API tokens disabled when Atlassian Guard is enabled

In the 11.5 release notes, we announced our plan to disable Jira Align API tokens when you've configured Atlassian Guard with Jira Align. As a preliminary step, when you configure Atlassian Guard as the authentication method in Jira Align, the ability for users to generate Jira Align API tokens and your existing Jira Align API tokens are disabled. You will still have the ability to re-enable the Jira Align API tokens through the API token security setting, if needed.

Changes to Start/Initiation and Target Completion fields

Following up on our previous announcement, we’ve made the following changes to the Start/Initiation and Target Completion fields found on themes, epics, capabilities, and features:

• Fields are set to always visible in details panels settings. If you’ve previously set these fields to hidden, they will now display inside details panels.
• The ability to lock and deactivate the fields has been removed.
• The fields are now located at the top of work item details panels, directly below the Program Increment field. Previously, the fields were located within the Full Details section of panels, requiring an extra interaction to make them visible.

We recommend implementing these fields in your processes, as they’ll be used as the source of truth for how dates display in the upcoming new roadmap experience.

Pagination added to sprint view of story backlog

To improve the performance when viewing large lists of items, we’ve added pagination controls to the Kanban > Sprint view of the story backlog. You should now experience quicker loading times when loading this view.

Custom room filters

Multi-select program, solution, and portfolio filters are now available in the custom room. Users can select up 10 teams and filter the room accordingly. Please note that the contributing teams modal does not filter as it is intended to show all contributing teams.

Note: This feature was delivered in release 11.9.1 to resolve an internally-reported bug.

Filter by charts on risk ROAM report

You can now filter cards on the risk ROAM report by selecting a Risk of occurrence or Impact of occurrence value from one of the pie charts on the page. Settings inside the View settings menu will update after making a selection. You can clear these selections from the View settings menu.

Removal of WIP by step board report

As previously communicated, the WIP by step board, also known as the work in progress by step report, has been removed from Jira Align.

Budget field character limit match through API

When modifying a strategic snapshot’s budget through the API, the field will now accept values between -2,147,483,648 and 999,999,999,999,999. These limits have been updated to match values that can be entered through the UI.

Bug fixes

Last updated: March 14, 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.9.0

• Opening the portfolio room with an invalid portfolio ID in the URL would result in a "Whoops" error.
• Deleted sprints would display in the global search.
• Jira would set team assignments if the Allow Jira to update the team field for stories setting was set to to No.
• On the program board, features and dependencies would display multiple times when filtering by multiple tags.
• On the risk slide-out, themes were unassignable after filtering, pagination and other actions related to reloading the page.
• On the program increment scope change report, points weren't converted into team weeks according to estimation conversion settings.
• Platform terminology wasn't respected on the program tracking report.
• On the program tracking report, the tooltip when hovering over Escalations was incorrectly cropped.
• Team impediments weren't displayed on the program increment cleanup report.
• On the strategic driver allocation report, multi-program epics wouldn't display if tied to the selected portfolio through an additional program.
• The strategic driver allocation report would use forecast tab values for epic estimates at the program level when accessed from a portfolio context.
• On the strategic driver allocation report, sorting by the epics column would order objects incorrectly.
• On the strategic driver allocation report, estimates wouldn't count for drivers when adding an epic without a strategic driver set up.
• On the program increment progress report, the Extra Configs button with a release vehicle filter would display in the Drill Down view.
• Sprints associated with objectives in the legacy experience weren't selectable in the new objectives details panel and the OKR hub.
• In the OKR hub, users couldn't search for owners in the Owners fields.
• In the OKR hub, the Show only my goals/objectives toggle was switched off when the current user was selected in the Owners field.
• When opening an objective's details panel for objectives that had contributors already selected, an additional click was required to view other contributor options in the Contributors dropdown.
• When a non-super admin user accessed the new objective details panel or creation wizard, program increment options would display in the incorrect order.
• On the new portfolio and solution objective slide-out, the This program increment and Upcoming program increment lines in both the Program increment dropdown and the set field value would display twice if a comma was included in the PI name.
• Themes couldn't be reassigned when changing an objective's portfolio, which would prevent saving the objective in the new details panel experience.
• On the new objective details panel experience, when the target sync sprint field was turned off and the program increment field wasn't required, saving would fail if a PI with an anchor sprint was removed.
• On the new objective details panel experience, an error would display on the Override Score modal if no optional note was added.
• Predecessor and successor values would be removed when themes were opened and saved.
• On the dependencies page, the same list of dependencies would display in the Your Requests section when changing pages on the top grid.
• On the defect backlog, the total count of work items in the corresponding sprint wouldn't update when either Unassigned Backlog or the same program increment appeared twice on the page.
• Any user with access to the recycle or cancel bins could view all programs and program increments, even when not part of the portfolio or program.
• Any user with access to the recycle bin could restore or delete related to programs they weren't part of.
• Features associated with additional programs wouldn't display in the recycle bin.
• In the feature recycle bin, selecting one option in the dropdowns would incorrectly display all features.
• The recycle bin wouldn't open when large amounts of features or epics were added to the bin.
• On the theme backlog, epics added through quick add weren't displayed until the page was refreshed.
• On the capability backlog's Kanban state view, capabilities wouldn't display in the Unassigned Backlog section.
• In the API, changing the type for Releases from class to record would prevent duplicates from being filtered out.
• Identified and closed vulnerabilities related to copying work items.
• Identified and closed vulnerabilities related to creating users.
• Identified and closed vulnerabilities related to audit logs.
• Identified and closed vulnerabilities related to logging into Jira Align.
• Identified and closed vulnerabilities related to details panels settings.
• Identified and closed vulnerabilities related to goals.
• Identified and closed vulnerabilities related to creating features.
• Identified and closed vulnerabilities related to editing epics.

11.9.0.0307

• The enterprise scorecard balanced report was listed in the sidebar when the corresponding system role toggle was switched off.
• On the feature roadmaps, no features would display when filtering by release vehicles.
• On the feature roadmaps, objective names wouldn't display when grouping by objectives.
• On the feature roadmaps, grouping by team, state, business driver, theme, or parent wouldn't accurately display features under the corresponding group.

11.9.1

• When drilling down on the program increment progress report, the Predicted, Pessimistic and Optimistic lines weren't calculated on the Program by Epic view.
  
• The custom room team filter list would display contributing teams that users didn't have access to.