The Jira Align support guide provides an overview of the various help resources available for Jira Align, as well as guidelines for creating and monitoring support tickets, feature requests, and test instance refresh requests. We recommend reading this guide to assist you in creating better cases and getting issues resolved as quickly as possible.

Check it out in the Atlassian Community here.

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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: April 11, 2025 to include include bug fixes delivered during the week

Coming soon

Removal of value engineering functionality in 11.11

In version 11.11, we’ll remove value engineering functionality from Jira Align. This includes both the value engineering fields found in the Value tab of work item details panels and the value engineering report. These functions were previously designated as end-of-support status, and we’re ready to remove them from the app.

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

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.

Q1 2025 roadmap presentation

Check out what we're currently working on in our latest quarterly roadmap presentation. This quarter, we're delivering an async review on the Atlassian Community as we focus on preparations for Team '25. We expect to return to live roadmap calls later this year. 

Enhancements and features

These features for 11.10 were released to environments on the continuous release track on March 28, 2025, in version 11.10.0. The features will be released to environments on the bundled release track on April 11, 2025, in version 11.10.1.

Update on reintroduction of Jira connector sprint sync logic

We have paused the activation of the Jira connector sprint changes previously announced in 11.9.X release notes, as we investigate some reports of unexpected sprint assignment changes in Jira Align.

We are planning to reactivate the feature in a future release with additional changes that will account for the unexpected behavior. Review our full announcement for details on how this uncommon issue can occur, and steps you can take to see if you're affected. 

OKR hub enabled for all environments

We’ve enabled the OKR hub for all environments as the main place for managing and tracking objectives. This includes:

• The sidebar menu option has been renamed from Objectives tree to OKR hub.
• Users will land in the hub with the correct tier, team, and program increment selected in page filters, depending on navigation and sidebar selections.
• A spotlight tour on first visit to refresh how the Tier filter works, and how to access the legacy objectives tree page.

As previously announced, the legacy objectives tree page will be removed in version 11.13.

Review our post on the Atlassian Community for more about the benefits and launch of the OKR hub.

End-of-support status for legacy objectives tree

With the launch of the OKR hub, the legacy objectives tree page has been designated with end-of-support (EOS) status. While the page will remain available until version 11.13, we will no longer file or fix non-critical defects, focusing our development efforts on the new experience.

Removal of legacy pages

As previously communicated, we’ve removed the following pages from Jira Align:

• Admin task status page
• Standup attendance report

Bug fixes

Last updated: April 11, 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.10.0

• Exports of defects would not complete.
• When viewing the forecast page, incorrect work item terminology was displayed for epics when hovering on the Progress column.
• Users without the correct system role permissions were able to access the epic status report.
• When viewing the features grid page, the top navigation bar would disappear when sorting a column with pagination.
• Identified and closed vulnerabilities related to objective details panels.
• Identified and closed vulnerabilities related to creating risks.

11.10.0.0403

• Errors would display when navigating to a program using the sidebar.

11.10.0.0408

• Release vehicle Health fields would not save changes in details panels when using Google Chrome web browser. 
• Messaging displayed on the release vehicle roadmap when no release vehicles were found in the selected team hierarchy was incorrect.
• Identified and closed vulnerabilities related to story details panels.

Below is our upcoming release schedule. Sandbox and production environments will be unavailable during our maintenance window, which starts at 11:00PM EST on the day listed below and ends at 2:00AM EST on the following day.

Release tracks

Production environments are set to use the bundled release track, while sandbox environments use the continuous track. We recommend using this default setup for your environments, as it allows you to test new features released in a .0 feature release for two weeks in your sandbox environment. Those changes will then deploy to your production environment in a .1 maintenance release. 

Due to the nature of continuous software development, some changes are applied to environments outside of our normal release schedule. In order to urgently remedy reported issues, the following changes were added to Enterprise Insights version 11.9.1.3542 via a hotfix, which is available for download on Tuesday, April 8.

This hotfix should be applied by any on-premise environment running Jira Align version 11.9.X or newer with Enterprise Insights version 11.9.X.

Defect fixes

Jira Align's Enterprise Insights (EI) version 11.10 was deployed to environments on the continuous release track on March 28, 2025. It will then be deployed to environments on the bundled release track on April 11, 2025. The following changes are included in version 11.10:

Release highlights

Enhancements and features:

•  The Lean UX Canvas column in the Epic view (current_dw and export_dw) has been removed. 

Bug fixes:

• JIRAALIGN-8059: The Date Created column for themes inside Enterprise Insights was not being updated. 

Updated tables

Below is our upcoming release schedule for Enterprise Insights (EI). Sandbox and production environments will be unavailable during our maintenance window, which starts at 11:00PM EST on the day listed below and ends at 2:00AM EST on the following day.

See the Release calendar article for the schedule of releases for the Jira Align platform. 

On Wednesday, March 26, 2025, we identified an issue with the recently reintroduced Jira connector sprint sync logic, and deactivated the enhancement in both sandbox and production environments.

We expect to reactivate the sync logic in a future release, after adding changes that will prevent this issue. We’ll update this announcement and our release notes once a new version is identified.

Note: On-premise environments are not affected, as the activation of the logic was not included in upcoming version 11.9.1.

Review this announcement to understand if you may be affected, and the actions you can take to correct sprint assignments in Jira Align.

• Why we're pausing
• Conditions that caused unintended changes
• Root cause
• Actions you can take
• Actions we're taking

Why we’re pausing

In some cases, stories or defects in Jira Align can be incorrectly moved to the unassigned backlog after closing a sprint in Jira. The unexpected behavior only occurs when syncing from Jira to Jira Align; data in Jira is not affected.

Conditions that caused unintended changes

This issue only occurred when the following configurations were set and actions were taken inside of Jira:

1. The connected Jira environment used a workflow configuration that set work items with a “done” Status that did not have a status category of Done.
2. The sprint was then closed.

Root cause

When a sprint was closed in Jira, the connector searched for any open stories or defects in the sprint and moved them to the unassigned backlog. The connector was incorrectly identifying stories that appeared to be open, based on the Jira status category. Some Jira workflows may use a status to indicate completeness that isn’t assigned to the Done status category. When using such statuses, the workflow configuration usually writes entries to the Resolution and/or Resolution Date fields.

Actions you can take

For most Jira workflows, sprint assignments in Jira Align were not affected. If you use a status in Jira that belongs to the Done status category, no action is required.

If you use a “done”, “complete”, etc status in Jira that does not belong to the Done status category, the connector may have moved matching work items to the unassigned backlog in Jira Align. If you’ve set up your workflow in such a manner, you can search for affected items inside Jira Align by using Jira query language (JQL):

1. Navigate to the Jira integration tab inside Jira settings.
2. Enter the following JQL query:
   "issuetype IN ([insert issue type(s) here]) AND statusCategory != Done AND sprint = ([ID of sprint that was closed]) AND NOT IN (futureSprints())"

Once you’ve identified the items in Jira that meet this criteria, you can move them in Jira Align back to the correct sprint.

Actions we’re taking

We plan to correct this unexpected behavior by adding additional checks to the Jira connector’s sprint sync logic after closing a sprint:

• If Jira Status Category != Done, check additional fields for data.
  • If both Resolution and Resolution Date fields are empty, move the work item to the unassigned backlog in Jira Align.
  • If either Resolution or Resolution Date fields contain entries, do not move the work item in Jira Align.

We’ll provide updates once a new version is identified for reactivating the feature with these changes.

We’re excited to announce that continuous deployments have officially arrived with Jira Align version 11.8. This advancement will allow us to deliver critical updates more frequently and efficiently, ensuring that you receive the latest fixes as soon as they are ready.

More fixes, zero downtime

We can now deploy bug fix releases as often as daily, without impacting your workflow. Continuous deployments follow zero downtime deployment (ZDD) standards, so you'll continue to have access to your environment during an update.

What’s included

Currently, continuous deployments focus on resolving bugs that affect the core functionality of Jira Align. In the future, we plan to expand this scope to include connectors and other features, such as Enterprise Insights.

Only bug fixes and other changes to resolve issues will be included in these versions. Features, process improvements, and other planned changes will continue to be provided on our standard release schedule.

Stay informed

To stay informed about the issues resolved in each bug fix release, you can do the following:

For bugs that you’ve reported or impact your environment, watch the issue in our Jira instance, jira.atlassian.com. You’ll receive notifications as we progress on investigating and implementing a fix. Once a fix is tested and committed to a new version, an entry will be made in the Fix Version/s field.

You can view the current version your environment is running on the login screen, or through the About page, accessed from your avatar menu in the upper-right corner of Jira Align.

Additionally, every Friday, we will update the current release notes article with a list of bugs fixed during the week. Look for “Last updated:” at the top of each release notes article and at the top of the bug fixes section to see when additions were last made.

We are committed to continuously improving Jira Align and providing you with the best possible experience. Continuous delivery is a significant step forward in achieving this goal, and we look forward to your feedback as we roll out this new capability.

Check out the latest news on new Jira Align features and development efforts we’re working on. Our Q4 2024 Product Roadmap presentation is now available.

Note that you will need to be logged into our Help Center site to be able to access the recording. If you don’t already have a login, select the Sign up link to create a new one. This account is not tied to your Jira Align user credentials.

You can subscribe to three Help Center sections to receive notifications the instant release note articles are published:

• Main Release Notes: These articles contain compiled information on a Jira Align version, initially published for the 10.X.0 feature release and updated each additional release through 10.X.3.
• Supplemental Release Notes: These articles contain information on individual supplemental releases, published each release from 10.X.1 through 10.X.3.
• Enterprise Insights Release Notes: These articles contain release notes specific to Jira Align Enterprise Insights (EI).

We recommend subscribing to both the Main and Supplemental Release Notes sections to get weekly notifications on the latest Jira Align version.

What you need to do

To receive real-time release notes publication notifications, you'll need to create a Help Center account and follow the section or sections you want to receive notifications about. Please note, this will most likely be a different username and password than your Jira Align and Atlassian username and password. 

 To create an account (or reset your password if an account already exists), click the SIGN IN button on the Help Center (see the pink arrow).

Next, click the Sign up link, enter your name and email, and then click the Sign up button. You'll receive an email to finish setting up your account. If you receive a message that says a user has already signed up with the given email, click the Forgot my password link to reset your password.

Once logged in, from the Help Center home page, click the WHAT'S NEW section (bell icon).

Then click the header for the section you want to follow. Finally, click the FOLLOW button and then the New articles link.

That's it! As soon as we publish new release notes, you'll receive an email notification with a link!