The Atlassian Jira Align team is pleased to announce Jira Align v.11.4.
Last updated: October 11, 2024 to include bug fixes delivered in bug fix release 11.4.1
Coming soon
Removal of 40+ Jira Align pages and functions in 11.5 and beyond
Following up on our end-of-support announcement from last year, we’re preparing to remove the remaining functionality that is no longer supported in Jira Align. We’ve updated the announcement’s table to help you view which items have previously been removed, and which will be removed in version 11.5 or later.
The following items will no longer be available as of version 11.5, which first ships to test environments on October 25, 2024:
The following remaining items will be removed sometime after version 11.5. We’ll provide additional notice in future release notes when a timeline is set.
Program room capacity-based widget and calculations toggle removal moved to 11.5
The planned removal of capacity-based widgets and calculations in the program room has been moved out one release to version 11.5, which will first ship to test environments on October 25, 2024.
In version 10.130, 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.
As of version 11.5, the new widget and calculations will be active for all users in your environment.
Note: You will no longer have the ability to override program PI velocities from widgets.
API: Replacing the Milestones endpoint paused
The planned replacement of the Milestones API endpoint has been paused while we work with you to understand your needs for migration and use of the Objectives endpoint. We’ll provide an update in future release notes when ready to set a new timeline.
As part of the recent release of the Milestones tab, we will be replacing the Milestones API endpoint with the Objectives endpoint. All endpoint functionality will remain the same and provide the same data. The only change will be the naming and URL. Please encourage your users to utilize the objectives endpoint.
Enhancements and features
These features for 11.4 were released to environments on the continuous release track on September 27, 2024, in version 11.4.0. The features will be released to environments on the bundled release track on October 11, 2024, in version 11.4.1.
Log into Jira Align with your Atlassian account
If you have a subscription to Atlassian Guard, you can now set Jira Align to use your Atlassian account credentials for logins. Atlassian Guard provides a single source for connecting user authentication with your SAML single sign-on (SSO) provider and also offers a two-factor authentication (2FA) option. This option is only available on Jira Align cloud. Atlassian Guard is included with a Jira Cloud Enterprise plan.
To enable Atlassian Guard, you’ll need to change your authentication method in your security settings. When enabled, users will be redirected to id.atlassian.com to log in. Manual login to Jira Align or stand-alone SSO logins are not available with this option.
This authentication option matches the Atlassian Account ID (AAID) in the External ID field in user accounts in Jira Align with the Atlassian account in Atlassian Identity. By default, the AAID is set to auto-populate the first time a user logs into Jira Align and authenticates with Atlassian Guard. Jira Align also enforces the session timeout durations configured in your Atlassian Guard subscription.
This new option simplifies the administration of SSO across all of your Atlassian cloud products and enhances the experience when switching between Jira Align and other Atlassian cloud products. Another benefit of this option is that you will be able to leverage new security features released on the Atlassian cloud platform with Jira Align.
Changes to security settings
To support this new feature, we’ve updated some setting names, values, and visibility in platform security settings:
-
Enable SSO renamed to Authentication method
-
No renamed to Manual sign in
-
Yes renamed to SAML single sign-on (SSO)
-
Atlassian Guard added as a new value
-
Auto-populate Atlassian Account ID (AAID) added as a new setting when Atlassian Guard is selected as the authentication method.
- SSO-specific settings have been changed to hidden unless the SAML single sign-on (SSO) option is selected as the authentication method:
- Disable Manual Sign In
- SAML 2.0 Identity Providers - Add SAML Provider
- Sign In URL
- Sign Out URL
- Privacy Policy URL
- Show Jira Align SAML 2.0 Service Provider metadata
Use Atlassian API tokens to authenticate with the Jira Align APIs
When you set up Atlassian Guard to use your Atlassian account credentials for Jira Align logins, you now have to ability to use Atlassian API tokens to authenticate with the Jira Align APIs. You can create an API token through your Atlassian account. See Manage API tokens for your Atlassian account for instructions on how to create Atlassian API tokens. We recommend that you switch from using the Jira Align API tokens to the Atlassian API tokens so you can take advantage of security features for the Atlassian API tokens such as revoking and blocking token access and new features rolled out in the future.
Blocked field on new objective details panel
On the new objective details panel, we’ve added a Blocked boolean field and a Reason text area field so that you can easily view and update the blocked status of an objective. If Blocked is set to Yes, the Reason field is required. The blocked data will be the same in both the new and legacy objective details panel.
Accessibility improvements through NodeJS and ADS upgrades
We’ve upgraded our infrastructure to use a more recent version of NodeJS, as well as the latest revision of the Atlassian Design System (ADS). This enhancement provides better accessibility for users in terms of contrast, highlights, and font size. You’ll notice these visual improvements across many of our newer pages and features. No changes have been made to logic, calculations, or general use of Jira Align.
Examples of changes include:
- Increased contrast on top menu bar items, form elements, and buttons in a hover state.
- Increased contrast and selection highlight on sidebar links and some dropdowns.
- Increased font size from 12px to 14px in some dropdowns, notably the sidebar program increment dropdown.
Delivered suggestions
Increased character limit in epic Additional Programs field
As part of delivering suggestion JIRAALIGN-7251, we’ve increased the text limit on the Additional Programs field for epics. Previously, the limit was 1000 characters. The new limit of 4000 characters will accommodate large lists of additional program assignments.
Task and Defect information added to the Jira change log
As part of delivering suggestion JIRAALIGN-6513 We’ve enhanced the Jira change log to include task and defect sync errors. Task and defect work items sync errors between Jira and Jira Align should now be logged in the Jira Change log under Jira Settings > Manage Projects > View Log, similar to features and stories.
Bug fixes
Last updated: October 11, 2024 to include bug fixes delivered in bug fix release 11.4.1
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.
Key |
Summary |
Release Version |
JIRAALIGN-5902 |
Jira Connector - Jira Align to Jira issue sync fail when having multiple Projects to a feature using T-shirt |
11.4.0 |
JIRAALIGN-6586 |
Inaccurate Label for Settings >> Jira Setup >> Does creating stories in Jira allow both an assignee and reporter assignment? |
11.4.0 |
JIRAALIGN-6679 |
/Connectors endpoint pulls from outdated data |
11.4.0 |
JIRAALIGN-6825 |
Saving a dependency with multiple programs gets error "Text Length Exceeded - 100 Characters " |
11.4.0 |
JIRAALIGN-7009 |
Multi-program Dependencies do not appear in Items > Dependencies |
11.4.0 |
JIRAALIGN-7172 |
Dependency grid does not display dependencies associated with Portfolio Epics and Capabilities |
11.4.0 |
JIRAALIGN-7233 |
In the r11.0 Release Note, when moving to the backlog within the completed sprint, the stories remain in the closed sprint. |
11.4.0 |
JIRAALIGN-7246 |
Field Management: unable to sync custom field (select) on Features from JA to Jira |
11.4.0 |
JIRAALIGN-7381 |
View Trends Bug Misleading 'No Data to Display' Message in OKR Charts |
11.4.0 |
JIRAALIGN-7468 |
Connector: Users are added to teams with the option on the connector disabled |
11.4.0 |
JIRAALIGN-7543 |
Portfolio(and PI)-specific Theme Backlog Audit log doesn't show the portfolio (and/or PI) |
11.4.0 |
Internally-found issues
We’ve corrected the following bugs that were discovered while investigating related issues, building new enhancements, and performing maintenance:
11.4.0
- OKR hub: Teams were not displayed in the All teams dropdown when navigating to the page from a higher-level context.
- OKR hub: Program increments were not displayed in the All program increments dropdown when navigating to the page from a solution or portfolio context.
- OKRs: Tags, creation date, and publish date data was removed when updating an objective through the API.
- Goals: An error message displayed when attempting to delete a goal associated with multiple snapshots.
- Work tree: When using the Theme Group view, incorrect items were displayed when filtering by portfolios, solutions, or programs.
- Themes: Duplicate records regarding process step changes were captured in the audit log after saving edits.
- Epics: Epics could be created with an empty required Theme field.
- Features: Edits to a feature were not saved if the feature’s name was changed to match an existing feature.
- Work item details panels: Saving changes would fail when attempting to add a link to a work item with a matching ID in the Links tab.
- Program increment progress: Pagination was not displaying properly when using the drill-down charts.
- Program increment progress: In the drill-down theme burnup chart, the Scope line was not counting points from epics not associated with a theme.
- Program increment progress: Drill-down charts would not render when orphan stories were found within a program.
- Stored XSS security vulnerability potential related to enterprise hierarchy grid was identified and closed.
- Stored XSS security vulnerability potential related to managing projects in Jira connector settings was identified and closed.
11.4.0.1004
- Objectives: Inconsistent colors displayed in guide panels after switching to the new creation experience.
- Performance slowdowns related to Atlassian Guard authentication were identified and closed.
- Infinite loop security vulnerability potential related to markdown text was identified and closed.
11.4.1
- Objectives: The Blocked reason field on blocked objectives was labeled incorrectly. The field name has been shortened to Reason.
- Objectives: Blocked objectives could be completed.
- Objectives: The selectable area of the Blocked radio buttons was too large.
- SQL injection vulnerability potential related to assessments was identified and closed.
- Defect: Find Story field on slide-out didn't display stories with special characters in the title.