Release notes for 11.5.X

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: November 27, 2024 to include bug fixes delivered in hotfix release 11.5.1.1126

Coming soon

11 pages and functions planned for removal in 11.8

In version 11.8.X, which first ships to environments on January 24, 2025, we plan to remove 11 pages and functions from Jira Align.

After reviewing recent usage data, it became clear that this functionality was not providing significant value. By removing this functionality and streamlining our codebase, we’ll have more capacity to address defect fixes across the product. These changes will also reduce our testing overhead, which will allow us to build and ship enhancements more rapidly.

Functionality that will be removed:

• Import/export for tasks only
• Brainstorming
• Lean process
• Multi-bottom-up forecast
  
• Resource planning
• Specifications
• Surveys
• The UX/UI landing page
• Pages related to UX/UI:
  • Design components
  • Experience maps
  • Lean use cases

System role permission toggles related to these pages and functionality will also be removed.

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.8.X to archive your data. You can use screenshots and Save options from your browser to capture the contents of a page.

Enhancements and features

These features for 11.5 were released to environments on the continuous release track on October 25, 2024, in version 11.5.0. The features will be released to environments on the bundled release track on November 8, 2024, in version 11.5.1.

Action required: Changes to Jira connector endpoints for Jira Data Center

Starting with the 11.5.0 release, Jira connectors connected to Jira Data Center will make use of a new endpoint: POST /rest/agile/1.0/epic/{epicKey}/issue for updating parent epic links for stories.

If you’re syncing Jira Align with Jira Data Center, make sure this endpoint is allow-listed in your proxy, API gateway, WAF (Web Application Firewall), or any other technology that filters access to your Jira Data Center instance. If you have already allowlisted wildcard endpoints, no action is required on your part.

Please ensure that the following wildcards are present in your allowlist so that all endpoints used by the Jira connector can be properly accessed:

• /rest/agile/1.0/*
• /rest/api/2/*

The Jira integration guide contains the different URLs we require for Jira Data Center integration.

If you have questions about how to allowlist the necessary endpoints or how to check if they're already allowlisted, raise a support request.

Atlassian editor and improved rich text sync for feature descriptions

We’ve improved the editing and viewing experience for feature work items that sync with Jira.

• We’ve added the Atlassian editor to feature descriptions. Take advantage of enhanced formatting capabilities like tables, code blocks, info panels, and more.
• Rich text now syncs between Jira and Jira Align for feature descriptions. Formatting that you enter in one tool will show up seamlessly in the other tool. Edits you make will sync back-and-forth between tools.

Enterprise Insights administration

If you’re using Enterprise Insights Cloud, you are now able to manage your Enterprise Insights instance through the Jira Align administration. The Enterprise Insights administration feature is only accessible by Jira Align Super Admin users.

To help you through the initial set up of Enterprise Insights, you can access a setup wizard that walks you through step-by-step on how to add firewall rules to allowlist your NAT IP addresses and user access using Microsoft Entra authentication. Microsoft Entra (formerly known as Azure Active Directory) authentication enables you to invite users in your active directory to access Enterprise Insights and login using your single sign-on and multi-factor authentication.

Note: This feature will be enabled in test environments on Monday, October 28, 2024.

Through the new Enterprise Insights administration pages, you can edit and delete firewall rules (IP allowlist) and Microsoft Entra user access that were previously set up.

The Enterprise Insights administration also has an audit log that allows you to view all historical records actions completed through the administration pages.

SSO login improvements

The SSO relay state early access program (EAP) has been made available to all cloud environments. Previously, SSO authentication logins would direct users to the home page in Jira Align after sign on, even when attempting to access a specific page through a link or bookmark. Now, users will be navigated directly to the linked page after signing on with your SSO provider.

If you notice any compatibility issues or other erroneous behaviors with this change, raise a support request.

Jira connector: new field requirements

As part of resolving JIRAALIGN-7094, the Project Key and Project Name fields on the Jira Settings page are now required when adding a new project to the connector.

Jira connector: changes to story parent sync logic

To resolve JIRAALIGN-7414, we’ve adjusted sync logic for connectors syncing stories bi-directionally . Now, removing the parent of a story in Jira Align will result in a sync to Jira, causing the story parent to be removed in Jira.

Previously, this action (removing the story of a parent in Jira Align) was not triggering a sync to Jira. As a result, subsequent changes to the work item in Jira or Jira Align could cause the removal of the story parent to be overwritten (and restored in Jira Align).

Removal of temporary portfolio room landing page

Note: This removal has been rescheduled for version 11.6.X

In the 11.1 release, we introduced a temporary portfolio and program room landing page for a subset of customers experiencing room performance issues. We are happy to share that over the last quarter we improved the portfolio room page load time by roughly 90% (from 13 seconds to 1.7 seconds). In this release, we’ll be removing the portfolio room landing page. The program room landing page will not yet be removed.

Removal of Jira Align pages and functions

Following up on our end-of-support announcement from last year, we’ve continued to remove the remaining functionality that is no longer supported in Jira Align.

The following items have been removed:

• Assessments
• Assessment report
• Business model canvas
• Capability maps
• Code reviews
• Code review groups
• Competitors
• Countries
• Customer visits
• Daily standup meeting
• Dashboard
• Defect suites
• Edit asset title
• Estimation games / estimation poker
• Feature maps
• Folios
• Folio viewer
• Functional maps
• Group metrics
• Innovation
• Journey maps
• Meetings calendar SOS
• Meetings list
• Metrics / Metric sheet
• Operational excellence vision
• Product vision
• Program increment defect trend 
• Program increment vision
• Sprint planning
• Sprint review
• Strategy dashboard
• Story maps 
• Team of teams meeting
• Team logos
• Velocity by certainty
• Velocity by complexity
• WIP by step (charts version)
• Workday

End-of-support status for legacy functionality

The work in progress by step report and value engineering functionality + report are now designated with end-of-support status. Jira Align Support will no longer file new defects for these capabilities, and we’ll prepare to remove the functionality in the future. We’ll provide at least 30 days notice when a timeline for removal is set.

Bug fixes

Last updated: November 27, 2024 to include bug fixes delivered in hotfix release 11.5.1.1126

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

• Program increment progress report: When viewing the burn up chart drill down theme view by team or epic, the chart for None Applicable would exclude some accepted stories in the accepted line calculation.

• Program increment progress report: When viewing the burn up chart drill down theme view by team accepted stories are not included in the accepted line calculation when viewing the report in the same day the stories were created.

• Program increment progress report: When viewing the epic drill down view and there are no epics, a 404 error would display.

• When opening a child objective from its parent’s details panel, the value in the Tier field wouldn’t display.

• Objective parent assignments weren’t displayed when a user didn’t have permissions to the parent objective tier, and would be removed (together with the parent key result) when the user saved the objective.

• In the strategy room, the epic count would display for capabilities in the Snapshot Progress widget.

• The Find Story field on defect details panels wouldn’t display stories with special characters in the title.

• On the epic backlog, when the sidebar was set to All time, the total counts of work items in programs wouldn’t change when work was dragged and dropped.

• The feature audit logs wouldn’t display additions or changes to a feature’s report color.

• On the epic backlog, creating a new epic using the Create button after an existing epic had been open and closed would cause the creation slide-out to be blank.

• Cyrillic and Chinese characters in feature titles and descriptions would display as ??? after the feature had been created.

• When adding stories to a feature, stories in the program that were already added to a feature would be available for selection in the Quick Add section.

• Stored XSS security vulnerability potential related to roadmaps was identified and closed.

• Performance slowdowns related to capacity plans were identified and closed.

• Users were unable to load more than 100 items on forecasts.

• Users were unable to create link maps.

• XML external entity injection security vulnerability potential related to licensing was identified and closed.

11.5.0.1101

• Link maps couldn't be created or updated.
• The Product Mapping section didn't display on the Azure DevOps Settings page, making it impossible to set mappings for the Product field.
• Vulnerability potential related to portfolios was identified and closed.

11.5.1

• API 1.0 endpoints didn't authenticate with Atlassian Guard.

11.5.1.1122

• "Whoops" error would display when navigating across enterprise pages after selecting a program increment and snapshot.
• "Whoops" error would display when creating dependencies with multiple program associations.
•