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

• Coming soon
• Enhancements and features
• Bug fixes

Last updated: Jan 10, 2025 to include bug fixes delivered in maintenance release 11.7.1

Coming soon

An update on the Portfolio Ask field

Back in August, we announced that we planned to remove the Portfolio Ask field and migrate its contents to new milestones within your work items. We planned these changes as part of work to display milestones more prominently on the roadmap and across Jira Align.

Since this announcement, we’ve been engaging with you on how to use milestones in a way that is more aligned the future of Jira Align. We’ve also removed portfolio ask from Enterprise Insights data, and replaced it with milestone views and columns.

Based on these conversations, we understand that some of you aren’t ready to migrate data to milestones. We have decided to pause the removal of the portfolio ask field, and do not plan to migrate this data.

The portfolio ask field is now considered end-of-support. We will not file or fix any reported bugs against it, and it will remain unavailable in Enterprise Insights.

We will provide additional updates when we set a timeline for removing the field in the future. To focus on building new features that compliment milestones, this removal won’t be considered for at least one calendar year.

To take full advantage of our future work, we still recommend moving your portfolio ask data to milestones, and to create milestones that represent portfolio ask dates on new work items.

/<work item>?isRecycled=false&%24filter=portfolioAskDate%20ne%20null

<work item>/<work itemid from step 1>/milestones

{
"title": "<title here>",
"description": "<optional>",
"state": <1 is pending, 5 is completed>,
"startOn": "<optional>",
"targetOn": "<copy paste portfolio ask date here>"
}

Custom room filter improvements

To address early feedback on custom room filters and avoid releasing this change over the holidays, the release of the custom room filtering improvements has been postponed to early 2025. The multi-select portfolio filter will also be included in the same version.

Additional removals of end-of-support pages and functions in 11.8

In version 11.8.X, we’ll be removing two features from Jira Align that were previously designated with end-of-support status.

• Mind maps
• Object promote

These pages and functions will be included with the previously announced removals for 11.8.

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.

Changes to Start/Initiation and Target Completion fields in 11.9

In version 11.9.X, we’ll make the following changes to the Start/Initiation and Target Completion fields found on themes, epics, capabilities, and features:

• The fields will be set to always visible in details panel 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 will be removed.
• The fields will be moved near the top of work item details panels, directly below the Program Increment field. Previously, these fields were located within the Full Details section of panels, requiring an extra interaction to make them visible.

We’re moving these fields and promoting their visibility to make them easier to locate and edit. 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.

End of support for legacy objectives tree in 11.10

In version 11.10, we’ll be ending support for the legacy objectives tree in Jira Align. Three months after that, in version 11.13, we will remove the legacy objectives tree page. We are sunsetting this page as the OKR hub is a streamlined, improved version of the objectives tree experience, and will reduce confusion about which page to view and track objectives.

As part of this rollout, we will enable the OKR hub feature toggle for all customers in version 11.8. The legacy objective tree page will still be accessible until version 11.13 by selecting the Go to objectives tree button.

We welcome feedback on the OKR hub as we roll out the removal of the legacy objectives tree.

Upcoming removal of the admin task status page in 11.10

In version 11.10, we’ll be removing the legacy admin task status page from Jira Align. We’re removing this unused page as it does not provide any actionable data for cloud or on-premise environments.

Enhancements and features

These features for 11.6 were released to environments on the continuous release track on December 20, 2024, in version 11.7.0. The features will be released to environments on the bundled release track on January 10, 2025, in version 11.7.1.

Updates to our release practices in preparation for continuous deployment

To prepare for continuous deployment coming to Jira Align in early 2025, cover more bugs in each on-premise release, and streamline our release notes content, we’re making the following updates to our release practices:

• On-premise versions will now be available for download one week later, 19 days after a maintenance release deploys to the bundled release track.
• All contents of feature, maintenance, bug fix, and hotfix releases can be found in a single release notes article.
• The release calendar will be simplified to focus on planned feature and maintenance release dates.

Review our full announcement for details on these updates, and steps you can take to ensure you receive real-time updates for the bug fixes that affect you.

Modernized strategic driver allocation report

We’ve given the strategic driver allocation report a major overhaul. The report has a new, modernized UI with new features and enhancements that improve the usability of the report.

• Complete chart make-over.
• New feature estimate allocation chart that provides the allocation of feature estimate by strategic driver.
• An updated epic table with column sorting and enhanced pagination.
• New feature estimate, story point estimate and accepted story points columns in the epic table.
• A new strategic driver filter to make the report easier to view epic data.

New OKR hub columns

We’ve added critical data to the OKR hub to make it a one-stop shop for all things objectives. As part of this release, we’ve added four columns:

• Planned value
• Delivered value
• Anchor sprint
• Blocked

Now that we have unlocked key data points in the OKR hub, and made it the page for tracking and reporting objectives, we will be beginning the removal process for the objectives tree page. More information about the transition is located in the Coming soon section of these release notes.

Track dependencies with tags

We added a tags field on dependencies so you can track dependencies by tag in the dependencies grid. Entering text in the search field of the dependencies page will search dependency titles and tags for a match. You can also add tags as a column on the dependency grid in the Columns Shown menu.

New objective details panel configurable in details panel settings

As part of bringing the new objective details panel to parity, we’re happy to announce the new objective details panel supports configuration of active and required fields through details panel settings.

If you’re interested in turning on this new and improved objective details panel in your instance, reach out to your Support team. Once turned on, individual users can switch between the new and legacy details panel experiences.

Action required: Additional changes to Jira connector endpoints for Jira Data Center

Starting with version 11.7.X, Jira connectors will make use of a few new endpoints:

• POST /rest/agile/1.0/sprint/{sprintId}/issue
• GET /rest/agile/1.0/board/{boardId}/sprint

Over the next couple of releases, we will begin using the PUT /rest/agile/1.0/issue/rank endpoint as well.

If you’re syncing Jira Align with Jira Data Center, make sure these endpoints are allowlisted in your proxy, API gateway, WAF (Web Application Firewall), or any other technology that filters access to your Jira Data Center instance.

We recommend adding the following wildcards to your allowlist so that all endpoints used by the Jira connector can be properly accessed:

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

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

Bug fixes

Last updated: Jan 10, 2025 to include bug fixes delivered in maintenance release 11.7.1

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

• The build number on the About page was always listed as 1.0.0.0.
• On the sidebar, the Teams option would display multiple times under More items.
• Identified and closed a vulnerability related to the strategic driver report.
• On the status reports, some dropdowns wouldn’t display under Extra Configs after applying changes on the stand-alone feature’s slide-out panel.
• On the program increment progress report, stories were counted on the burndown charts if they had been dropped from the program increment with their parent feature.
• On the homepage, duplicate room cards would display in the Recent rooms section.
• On the ideation portal’s idea details panel, the words “product” and “idea” wouldn’t display for external users.
• When creating a dependency for a capabilities, adding a second program in the Depends On field would result in a “Whoops” error.
• On the work tree, all release vehicles would display in the filter dropdown lists when no program increments were selected in the sidebar.
• On the work tree’s theme group view, all epics would display in the filter dropdown lists when no program increments were selected in the sidebar.
• The work tree’s theme group view wouldn’t display when more than one program increment was selected in the sidebar.
• On the OKR hub, an error would display when switching from the objectives to the goals level columns were displayed in the table.
• When removing the Theme column from the exported file for epics and then importing epics back, the themes were removed from the epics they were assigned to.
• On the new objective details panel experience, key result score change weren’t recorded in the audit log when a key result's baseline and goal values were updated.
• A Jira connector API response parse error prevent would prevent data from syncing.
• Identified and closed a vulnerability related to the Azure DevOps connector.
• On the feature backlog’s Kanban value stream view, users couldn’t move features between programs without mapping to external systems.
• The word “feature” on the feature mass move audit log wasn’t tied to platform terminology.
• Identified and closed permissions vulnerabilities related to Kanban boards.
• In the Kanban view of the capability backlog, incorrect numbers would display in the Process Step column when filtering by custom hierarchy.

11.7.1

• On the new objective details panel experience, themes couldn't be added to an objective when the Themes field was required.
  
• On the new objective details panel experience, required fields didn't display with red asterisks.
• On the strategic driver allocation report, when no strategic drivers were allocated for a program increment, the Driver dropdown would display with no value, even if the epics had associated drivers.
• Identified and closed a vulnerability related to audit logs.
• Identified and closed a vulnerability related to process flows.

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. 

Note: This article has been republished in order to provide notification to users subscribed to updates in Enterprise Insights release notes. This article has been updated to include additional bug fixes and notice of upcoming column removals in version 11.8. 

Jira Align's Enterprise Insights (EI) version 11.7 was deployed to environments on the continuous release track on December 20, 2024. It will then be deployed to environments on the bundled release track on January 10 6, 2024. The following changes are included in version 11.7:

• Release highlights
• Coming soon

Release highlights

In version 11.7, the following changes were made:

Bug fixes:

• JIRAALIGN-7726: export_dw.[Epic Milestone] didn't set [Deleted Flag] when the associated epic was deleted.
• JIRAALIGN-7738: Large values on the epic intake's Benefit tab would prevent the SSIS ETl from fully running.
• JIRAALIGN-7835: Data discrepancy in Epic Milestone view and Jira Align UI.
• JIRAALIGN-7863: Team level forecast values not present in the Feature Forecast view for teams associated to an additional program.

Coming soon

In version 11.8, the Team ID and Program ID columns will be removed from the Jira Board view in the current_dw schema. 

We're making this change as the Team ID and Program ID columns store the same foreign key values as the FK Team ID and FK Program ID columns. This change resolves issue JIRAALIGN-7885.

Please update your queries and reports before version 11.8 to use the FK Team ID and FK Program ID columns in the current_dw.Jira Board view.

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. 

Following up on our changes to support Jira Align version 11.X, we’re announcing additional enhancements to our release practices. These updates will provide us with more ways to ensure code quality and fix issues quickly, while giving you better access to release contents.

We’re also making these changes to prepare for continuous deployments of Jira Align, which will allow us to rapidly ship bug fixes as soon as they’re ready, instead of waiting for a Friday release.

Review this announcement to understand how to quickly find details on what we release each cycle, and how to get real-time notifications for bug fixes you care about.

• Now: Updated timing for on-premise releases
• Now: A single article for release notes and a streamlined calendar
• Soon: Continuous deployment for bug fixes
• How to prepare

Now: Updated timing for on-premise releases

Beginning with 11.7.X, on-premise release versions will be available for download one week later. This shift allows us to include fixes for any bugs discovered during a version’s entire life cycle, before code is delivered to on-premise environments.

• On-premise environments will receive a new version 19 days after the version is shipped to production environments.
• New on-premise versions will continue to be provided on Wednesdays.

Now: A single article for release notes and a streamlined calendar

Also beginning with 11.7.X, you can find all information about a version's features, improvements, and fixes in one location.

• All contents of a feature release and its subsequent maintenance, bug fix, and hotfix releases will be contained in a single article, such as Release notes for 11.6.X.
  • As new fixes are delivered each week, we’ll continue adding this information to the bug fixes section of the page.
• We will no longer create standalone articles for bug fix and hotfix releases.
• The feature release notes section in Help will be renamed release notes.
• The bug fix release notes section in Help will be retired sometime in 2025.
  • Any bug fixes added to major versions 11.X and later can be found in the corresponding release notes article.
• Any release schedule changes, rollbacks, or other important updates that require a separate article with notifications will be posted in our announcements section.

Now that all release contents can be found in a single article, we will no longer include entries in the release calendar for optional bug fix and hotfix releases. Use the calendar to focus on planned deployments and quickly access a release notes article for a specific version.

Soon: Continuous deployment for bug fixes

Sometime in early 2025, we’ll begin deploying bug fix releases as soon as a new version is ready. We may release as often as once per day, getting fixes into your environments quickly. We’ll make an announcement with more details when this change is ready to launch.

Only fixes and critical changes will be contained in these continuous deployments. New features and planned changes will continue to be delivered on our current cadence, using our Friday maintenance window.

How to prepare

No action is required for these current and upcoming changes. However, you can prepare for continuous deployment by adopting the following practices now:

• Subscribe: Make sure you’re getting notifications of new release notes and announcement articles by subscribing to the release notes and announcements sections in Help.
• Review: You can get a recap of what we’ve deployed each week by visiting the latest release notes article. We’ll update the contents of articles each Friday when there are reportable changes.
  • 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.
• Watch: If you’re affected by a particular bug, view the issue at jira.atlassian.com (JAC), and select the Start watching this issue link in the upper-right corner. This will notify you of any changes, including deployment of the fix. We’ve enhanced JAC with a connector to our development environments, providing real-time updates the moment a version containing a specific fix is deployed.

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.

We’re removing the Portfolio Ask field from themes, epics, capabilities, and features in Jira Align. Although we do not have exact timing for removals yet, the field will remain until at least November 22, 2024, when we first deploy version 11.6.X to test environments. We are letting you know now so that you have ample time to prepare, and will provide another notice once an exact version for removal is confirmed.

We are removing portfolio ask as part of our work to evolve the roadmap page and simplify the product. This removal is part of our broader effort to streamline the user experience.

Portfolio ask does not surface on the roadmap today, nor will it in the future. Instead, we are working to more prominently display milestones on the roadmap and across Jira Align. We believe milestones effectively solve the need of portfolio ask while also offering more information and functionality.

As such, we are planning to migrate all portfolio ask dates that are part of work items to milestones. This migration will take place in the version that we set for future removals. We will create new milestones for environments with portfolio ask dates with the following information:

For accepted work items:

• Name: Portfolio ask
• Description: Migrated by Jira Align
• Category: None
• State: Completed
• Start date: None
• Due date: The portfolio ask date

For all other work items:

• Name: Portfolio ask
• Description: Migrated by Jira Align
• Category: None
• State: On track
• Start date: None
• Due date: The portfolio ask date

We understand this change may require process adjustments for some organizations. To ask more about our migration, please raise a support ticket titled, “Portfolio ask migration.” We also recommend updating your queries and custom reports that use portfolio ask data in Enterprise Insights (EI) over the next couple of months, as the field will also be removed from EI.

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!