Release notes for 11.3.X

Note: This article has been republished. This method is used to notify users subscribed to feature release notes of new content and changes. This article has been updated to include the planned availability of a new early access program for SSO login improvements.

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

• Coming soon
• Enhancements and features
• Performance improvements
• Bug fixes

Last updated: October 4, 2024 to include bug fixes delivered in bug fix release 11.3.1.1004

Coming soon

Upcoming rollback of Jira connector sprint assignment logic

On Tuesday, September 3, 2024, we're planning to release a hotfix to roll back a previously-delivered Jira connector enhancement. We’re doing this in order to prevent unintended changes to story and defect sprint assignments in Jira. Because a specific combination of settings and actions in Jira Align can cause the unintended behavior to occur, you are unlikely to encounter this scenario.

Review our full announcement to understand if you may be affected, and the actions you can take to prevent unintended changes from occuring.

Early access program for SSO login improvements

We’re offering a preview of improvements to SSO relay state behavior through an early access program (EAP). This program will begin with version 11.3.1, which ships to environments on the bundled release track on September 13, 2024. Participating in the EAP will give you the ability to test these improvements to accessing pages in Jira Align after an SSO login, and provide us feedback that we can use to further support more SSO implementations.

Currently, our SSO functionality directs users to the home page in Jira Align after sign on, even when attempting to access a specific page through a link or bookmark. With the changes provided in the EAP, you’ll see the page you’re trying to access after signing on with your SSO provider.

If you would like to participate in the preview, please raise a support request with the title “SSO relay state EAP”. 

Reminder: Program room capacity-based widget and calculations toggle removal in 11.6

In version 10.130.X, we introduced a toggle at the top of the program room page, which enables a new widget, forecast vs. capacity. This new widget focuses on forecasted work vs. available program increment capacity, and replaces the program PI load (estimates view) widget. The toggle also streamlines the calculations for the program PI load (actual view) and team load widgets by utilizing information from the new capacity page and removing the need for manual overrides.

Due to the to the positive response to these changes, we will remove the toggle from the program room in version 11.4, which will first ship to test environments on September 27, 2024. At that time, the new widget and calculations will be active for all users in your environment.
Update: This change has been rescheduled for version 11.6, which will first ship to test environments on November 22, 2024.  

Note: You will no longer have the ability to override program PI velocities from widgets.

Future removal of the theme burnup chart in the portfolio room

In the 11.6.0 release, we’re removing the theme burnup chart from the theme program increment progress widget in the portfolio room. This chart is increasing page load times and has far less utility than the program increment progress report. The theme program increment progress part of the widget will remain.

Enhancements and features

These features for 11.3 were released to environments on the continuous release track on August 30, 2024, in version 11.3.0. The features will be released to environments on the bundled release track on September 13, 2024, in version 11.3.1.

Jira connector: sync Jira built-in teams field with Jira Align

We’ve added a new option to sync the built-in teams field in your Jira instance (Atlassian Teams in Jira Cloud or Shared Teams in Jira Data Center) with Jira Align. With this option, you can now get closer to the Atlassian platform by mapping Jira Align teams directly to the teams in Jira Cloud and Jira Data Center – without needing to maintain a separate custom field in Jira.

To set up team syncing with this option, use the Team custom field setting on the Jira Settings page. Selecting the Built-in field option will let you define the field ID for your Jira instance’s built-in teams field.

Then, use the API 2.0 to create, edit, and delete team mappings.

Try it out now: we’ll maintain your previous custom field mappings if you ever need to switch back to syncing with another custom field.

Enterprise Insights data file retrieval option

We’re offering a new option that lets you export your Jira Align cloud data from Enterprise Insights and import it into your own database or data lake. With data file retrieval, your Enterprise Insights data is exported to Apache Parquet formatted files that are stored within a dedicated Amazon Web Services (AWS) S3 bucket that only you have read access to. The data file retrieval option is offered as an alternative for when you are unable to use a Microsoft SQL Server client or compatible ODBC/JDBC client to access Enterprise Insights.

For more information on this option, review our documentation.

Release vehicle roadmap report location changes

To resolve an internally-discovered bug where data on the release vehicle roadmap page could not be loaded, we removed the report from the enterprise (strategy) level and added it to the solution, program and team level reports.

Additional columns available on dependencies page

We’ve added three new columns to the dependencies page, providing you with more ways to sort and monitor dependencies. You can display any of these columns through the Columns Shown menu:

• Created by: Displays the avatar of the user that created the dependency. Hover over the avatar to see more details about the user.
• Date created: Displays the date that the dependency was first saved.
• Last updated: Displays the date that the dependency was last edited.

Notes field on objective details panel

On the objective details panel, we’ve added a Notes text area field so that you can easily view and update critical objective information. The notes data will be the same in both the new and legacy objective details panel, and allows up to 2,000 characters.

Team, sprint, and user audit log improvements

We added team, sprint, and user audit logging when users are added or removed from teams and sprints.

Performance improvements

Program board performance improvements

The program board performance improvements early access program (EAP) was successful, and we’re excited to announce that these improvements are now available for all environments. We’ve optimized the SQL queries used to render the program board each time the page loads. With these changes, program board load times have been reduced by 50-90%!

Navigation menu performance improvements

We added pagination to the navigation menus to get team data in batches, versus a single, slow batch. Now, users with access to many teams will see faster load times.

Portfolio room performance improvements

This release includes two optimizations. First, we moved the quarterly impact roadmap to its own API endpoint so it loads in parallel with the page and all other widgets. Previously it was part of the page load, slowing load time. We also made the page read-only so that it no longer writes to session. Previously, 19% of all requests were waiting to write in session for at least 7 seconds. As a result of these changes, we expect users to see faster page load times.

Bug fixes

Last updated: October 4, 2024 to include bug fixes delivered in bug fix release 11.3.1.1004

User-reported issues

This list of resolved bugs will be updated weekly to reflect changes from maintenance and bug fix releases. You can see the contents of individual bug fix releases in the Bug fix release notes section.

Internally-found issues

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

11.3.0

• ActualEndDate will be synced by Jira connector. Previously it did not. This will affect past sprints that have been synced.
• On the strategic backlog, stand-alone features would display in the modal when changing an epic’s position.
• On the work tree, users without team membership could view all existing releases and work items at the strategy and product levels
• All programs were removed from themes if a user with access to a single program removed that program association from the theme.
• Filtering by a release vehicle on the work tree was unavailable if the release vehicle had been added to a group.
• The story State field label in our export files wasn’t formatted correctly, causing importing the files to fail.
• On status reports, the Value Score field didn’t match the Score field on the epic details panel for epics that were associated with more than one program.
• Stored XSS security vulnerability potential related to the program tracking report was identified and closed.
• Users couldn’t update dependencies to indicate that no work was required using the API 2.0.
• Users couldn’t create or update risks for epics, capabilities, and features associated with additional programs using the API 2.0.
• On the program board, special characters added to the objective platform terminology didn’t display correctly in the planning issue message.
• Work items wouldn’t display on the roadmaps when a custom room was selected in the top navigation bar or sidebar.
• Information on the release vehicle roadmap could not be loaded due to the page’s location at the strategy level.
• The Delete button would erroneously display when creating new use cases.
• Defects in the defect backlog couldn’t be sorted by category.
• After changing a feature’s report color, the change wasn’t reflected in audit logs.
• Stored XSS security vulnerability potential related to email logs was identified and closed.

11.3.0.0906

• SQL injection vulnerability potential related to the teams page was identified and closed.
• When updating themes associated with multiple programs, if a non-Super Admin user removed a single program association, the audit log would erroneously display an audit log message that other programs were also removed.
• On themes, if a non-Super Admin user didn't have access to one or more programs listed in the Program dropdown, those program assignments would be removed one-by-one from the dropdown when selecting the dropdown and then selecting Save.
• On the dependencies page, all epic and capability dependencies would display when filtering the grid by team as a Super Admin.
• On the forecast page, navigating to the page for a solution and then expanding a program increment as a non-Super Admin user would cause an Error on server message to display.
• On the capacity page, stand-alone features would be included in the Forecast versus capacity bar when the Show stand-alone features toggle was disabled.

11.3.1.0920

• After removing a program association from a theme, remaining associated programs were displaying as removed in the audit log.
• The Last Updated column on the dependencies grid page was not populating after updating a dependency. 
• Jira sub-tasks would fail to sync through the connector if Jira Align tasks with the same name were present. 

11.3.1.0927

• When creating a new dependency, the Associated Capability field would display empty after selecting a capability in the details panel.