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

• Enhancements and features
• Defect fixes

Enhancements and features

These features for 10.125 were released to environments on the continuous release track on September 29, 2023, in version 10.125.0. The features will then be released to environments on the bundled release track on October 13, 2023, in version 10.125.2:

New navigation: sidebar updates

• The lightbulb icon next to Objective Tree has been replaced with the bullseye icon.

• Page names now use sentence case. For example:

  • Objective Tree → Objective tree

  • Work Tree → Work tree

  • Program Board → Program board

New navigation: program board page updates

The program board page no longer requires scrolling to see the view configuration, full-screen, and legend buttons.

New navigation: homepage accessibility

The new homepage now supports skip links and tab indexes, and starring/unstarring pages now works through keyboard navigation.

New navigation: homepage accessibility

The new homepage now supports skip links and tab indexes, and starring/unstarring pages now works through keyboard navigation.

OKR hub accessibility

With the addition of column re-ordering and tab selection for dropdown menus, the OKR hub is one step closer to being fully accessible!

Column re-ordering:

• Use Tab to navigate through the table headers
• Pressing Space on a header will start reordering mode
• Use the left and right arrow keys to move the column
• Pressing Space again ends reordering
• Pressing Enter on a header will sort the column if it is sortable

Dropdown menus: 

• Use Tab and the arrow keys to navigate through dropdowns
• Press Enter to select an option in the dropdown

New API 2.0 endpoints and properties

To create parity with the API 1.0, we’ve added a few API 2.0 endpoints:

• New endpoint to create, read, update, and delete cost centers

• New endpoint to create, read, update, and delete work codes

We’ve also added new properties to the release vehicles API:

• releaseName
• StoriesPercentComplete
• StoriesCount
• StoryPointsTotal
• StoryPointsAccepted
• Total
DefectsCount
• ContributingTeamsCount
• ContributingProgramsCount
• Capabilities
• Portfolios
• productId

Quality module: Confirmed and upcoming object removals

In version 10.121.3, we removed the summary pages within the Quality module, while references to some objects remained. In this release, we’ve cleaned up the codebase and removed all references and links to sprint plans.

In version 10.126.0, we plan to fully remove references and links to test sets.

Defect fixes

The list of defect fixes will be updated to reflect changes in weekly maintenance releases. You can see the contents of individual maintenance releases in the Supplemental Release Notes section.

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

By default, production environments are set to use the bundled release track, while sandbox environments (previously known as test instances) 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 .2 maintenance release. 

You may change the release track from bundled to continuous in your production environment by submitting a request to our Support Team. Note that we do not guarantee a timeframe to make a release track change, but will strive to complete the request as quickly as possible. 

Due to the nature of continuous software development, some changes are applied to a version after it has been released to production instances. In order to urgently remedy a reported issue, the following change was added directly to version 10.124.3.20, which was deployed to all Jira Align environments on Friday, September 29.

Enhancements and features

New navigation - Multi-select team and portfolio filters added to Roadmaps

Multi-select team and portfolio filters are now available on the roadmaps filters modal. When using these filters, roadmaps will show work from all selected teams or portfolios.

Defect fixes

• Resolved an internally-reported defect where a shared filter error would display when selecting more than one portfolio in Apply filters.

The 10.124.3 maintenance release was deployed to environments on the continuous release track and environments on the bundled release track on September 22, 2023. Maintenance releases contain high-priority defect fixes and fixes for any features deployed in version 10.124.X.

Defect fixes

Jira Align's Enterprise Insights (EI) was updated and deployed to 10.125.X instances on the continuous track on September 29, 2023, and will be deployed to instances on the bundled track on October 13, 2023. The following enhancements were made:

• Release highlights
• Announcements
• Updated tables

Release highlights

• New content/suggestions

  • Removal of HTML tags in values for Objective Description in the Objective and Objective History views in the current_dw and export_dw schemas.

  • Removal of HTML tags in values for Feature Description in the Feature and Feature History views in the current_dw and export_dw schemas.

• Defect fixes

  • JIRAALIGN-5424 - Field Name column is not being populated with values in the Details Panels Setting view in current_dw schema.

    • To resolve this, we will remove the Test Suite Name column in the Test Case views (current_dw and export_dw schemas).

    • The removal is a result of the deprecation work of the Quality module in Jira Align. ITo prepare for these upcoming changes, make updates to your reports and dependencies (i.e. ETL) that use this field.

Announcements

• In Release 10.127, the following change will be made:

  • The Feature Type column in the Epic views (current_dw and export_dw schemas) will be removed.

    • The column name is inconsistent with the Epic History view, where the column name is Epic Type.

    • Please update your reports and integrations to use the new Epic Type column in the Epic views (current_dw and export_dw schemas), which became available in release 10.123.

Updated tables

Note: Due to a previously unreported feature, this article has been deleted and then republished. This method is used to provide notification emails to users subscribed to Release Notes updates. For more information about the additional feature, check out Inconsistent results for Sprint Team Member views within current vs. export schema.

Jira Align's Enterprise Insights (EI) was updated and deployed to 10.124.X instances on the continuous track on September 1, 2023, and will be deployed to instances on the bundled track on September 15, 2023. The following enhancements were made:

• Release highlights
• Announcements
• New tables
• Updated tables

Release highlights

• New content/suggestions

  • Character limit of the Sprint Short Name field in the Sprint table expanded from NVARCHAR(20) to NVARCHAR(50) to accommodate the expansion of the Short Name field in the Sprint details panel beyond 20 characters in Jira Align.

  • Character limits of the Custom Text 1 and Custom Text 2 fields in the Feature and Feature History tables respectively were expanded from NVARCHAR(250) to NVARCHAR(255) to accommodate the expansion of the custom text input fields for features to 255 characters in Jira Align.

  • Defect fixes

    • Inconsistent results for Sprint Team Member views within current vs. export schema:

      • We resolved an issue with inconsistent deleted users in the Sprint Team Member views. In this issue, even when users are not deleted, they appear to be deleted within the current_dw views and don’t display in export_dw views.

    • JIRAALIGN-5158: Approvers field and values are not stored in the Epic Benefits view.

    • JIRAALIGN-5129: Capability Attachment view is not storing updates made to the attachments on capabilities.

Announcements

• In version 10.125, the following change will be made:
  • The Test Suite Name column in the Test Case views (current_dw and export_dw schemas) will be removed.
    • The removal is a result of the deprecation work of the Quality module in Jira Align. In preparation for these upcoming changes please make updates to your reports and dependencies (i.e. ETL) that use this field to accommodate for the change.
• In version 10.127, the following change will be made:
  • The Feature Type column in the Epic views (current_dw and export_dw schemas) will be removed.
    • The column name is inconsistent with the Epic History view where the column name is Epic Type.
    • Please update your reports and integrations to use the new Epic Type column in the Epic views (current_dw and export_dw schemas) available in release 10.123.

New tables

Updated tables

Check out the latest news on new Jira Align features and development efforts we’re working on. Our Q4 2023 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.

In version 10.127.1, we’ll be finishing our rollout of Jira Align’s new navigation. The old navigation will be permanently replaced and will no longer be accessible. Additionally, old navigation information will be removed from our Help Center articles.

To prepare for the removal, we recommend switching to the new navigation and trying it out for yourself. You can also check out our articles about the new navigation and homepage to get familiar with the changes.

We also recommend updating any internal Jira Align documentation you may have with new navigation details by version 10.127.1. We’ve added new navigation information to our existing Help Center articles to help with this, as well as a PDF for a quick reference of all page locations in the new navigation.

Select the attachment below to download the PDF:

If you have an on-premise instance of Jira Align, please read the following and take action prior to installing version 10.123.3, which will be available for download on August 25, 2023.

What’s changing

Jira Align uses the SQL Server Native Client (SNAC) driver which is no longer recommended for use by Microsoft. Microsoft recommends switching to the Microsoft OLE DB Driver (MSOLEDBSQL) for SQL Server going forward.

We have tested and approved versions 18 of the OLE DB driver for use with Jira Align on-premise environments. 

Action required

Before installing Jira Align version 10.123.2, ensure that all web and connector servers in your environment are updated with the OLE DB Driver, version 18. The driver can be installed while any previous Jira Align version is running. You can download this version from the following link: OLE DB Driver for SQL Server v18

Jira Align is improving the way you navigate!

We’ve overhauled Jira Align’s navigation with faster, simpler paths to get to where you need to be. And, you’ll feel more at home with a new look that matches other Atlassian products.

With the release of version 10.122.0 on July 7, 2023, we’ll begin our rollout of the new navigation to sandbox environments on the continuous release track. Production environments on the bundled release track will receive the changes in version 10.122.2, which will be deployed on July 21, 2023.

You’ll be able to switch between the old navigation and the new navigation for a limited time after release.

Changes we're making

The new navigation includes:

• New information architecture oriented around what you already know - your teams.
• New top navigation bar to navigate hierarchies: the teams and functions you operate in daily.
• New sidebar to improve page discovery and accomplish top tasks. As you navigate across pages, your views will stay filtered by the selected team and scope.
• New homepage that provides quick access to your most important rooms and pages.

To learn more, check out the article in the Atlassian Community and release notes information.

Note: This article has been deleted and re-published to send a new notification, as the release timeframe for these changes has been updated.

For versions 10.100.1 and later, we'll be making some big changes to objective statuses that will also affect the API:

What’s coming in version 10.100.1

In this release, we will be adding three new statuses to objective tracking in Jira Align. These statuses will provide more nuance to the status of objectives than our current option (In Progress) allows. The new statuses will be:

• On Track: Indicates that an objective is likely to reach its desired outcomes.

• At Risk: Indicates that an objective has uncertainty around reaching its desired outcomes. For example, work needed to complete the objective may be behind schedule, or risks might pose a future threat to completion.

• Off Track: Indicates that an objective is unlikely to reach its desired outcomes if action is not taken.

In version 10.100.1, the new statuses will become available in the Jira Align UI, and will not change any existing status values. API users should also note that the status endpoint will include the new statuses, and no statuses will be removed or changed for this release.

We strongly recommend that you review your in-progress objectives and update any objectives that are at risk or off track, as the In Progress status on objectives will be migrated in a future release.

What’s coming later

In a future release, any remaining In Progress objectives will receive the On Track status. At this time, the API status value for In Progress will also be removed.

What this means for the API

Any objectives with the In Progress value will now return as On Track. There are also two new values: Off Track and At Risk. In any scenarios where the In Progress value is specified, there would need to be a change to specify On Track and depending on the use case, include the new status values as well. Otherwise, there is no action needed with this change.

Why are we making this change?
This change is in preparation for a new end-to-end objective experience including a new creation workflow, a cleaner Details panel, and a more powerful objective tree experience. As we continue to respond to feedback, it has been evident that we need the ability to provide better status updates around objectives.

For our customers utilizing OKRs, the objectives often appeared to be “at risk” when they had low scores, even if it was just too early in measuring. These new changes, along with the updates to the objective tree around the corner, will provide a much clearer picture of which objectives need attention (and which don’t) when reporting on status.

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!