Release Notes for 10.113.X

Note: Due to a deployment issue with 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. Please see the Objectives tree (new experience): Hierarchy view for goals section below for details. 

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

• Enhancements and Features
• Defect Fixes

Enhancements and Features

These features for 10.113 were released to environments on the continuous release track on October 21, 2022, in version 10.113.0. The features will then be released to environments on the bundled release track on November 4, 2022, in version 10.113.2:

.NET 6 required soon for on-premise instances

As previously announced, Microsoft will soon be ending support for .NET 3.1, which is required to install an on-premise instance of Jira Align. Please upgrade your environments to version .NET 6, no later than December 7, 2022, to ensure your infrastructure can support Jira Align version 10.114.2 and beyond. You may perform this upgrade as soon as possible.

Objectives tree (new experience): Hierarchy view for goals

We've updated the new objectives tree experience to show you the parent-child hierarchy for a selected goal. Select the Actions icon to the right of a strategic goal to display its hierarchy view. Parent and child items will display as cards, organized as a family tree. To view additional levels, select the green arrow icon next to a card. 

Objectives tree (new experience): Columns shown and Export buttons

We’ve added a Columns shown menu to the new objectives tree experience, above the grid of items.

Use this dropdown to show or hide the following columns on the page:

• Status
• Work progress
• Key results progress
• Key results
• Program Increment
• Owner
• Team
• Target Completion
• Actions

In addition, we’ve made exporting your data easier by creating a dedicated Export button, found next to the Columns shown dropdown. 

Objectives tree (legacy experience) enhancements

To align the way solution-level objectives work between experiences, we’ve updated the legacy objectives tree experience. Now, the Solution Objectives tab is visible when using the legacy experience, even when the portfolio selected in the Configuration bar has the Admin > Platform > Portfolio > Portfolio Specific Configuration > Enable Capabilities option set to No. Objectives may be linked in the following manner, depending on the Enable Capabilities setting.

Capabilities are not enabled

• Solution objectives may be parented by portfolio objectives.
• Program objectives may be parented by portfolio objectives.
• Program objectives may not be parented by solution objectives.

Capabilities are enabled

• Solution objectives may be parented by portfolio objectives.
• Program objectives may be parented by solution objectives.
• Program objectives may not be parented by portfolio objectives.

We also improved the consistency between experiences for the visibility of filters. Now, the legacy experience will display any selections made in the Apply Filters menu at the top of the page:

Features now on by default

The following list of the functionality previously required enablement by our support or services teams during the initial configuration of Jira Align. This functionality is now permanently enabled and no longer requires manual changes.

• The Why button may be used with a Jira Software connector custom field mapping, and when set up, syncs key information from Jira Align to teams working in Jira. This information answers questions like, "Why am I building this functionality, what strategy or objective is this tied to, and what is the value we’re trying to achieve?"

Jira connector timer minimum and maximum values

We added minimum and maximum values to Jira Software connector timer settings, to ensure optimal sync cycle times. If a timer setting is outside one of these new ranges, you’ll be prompted to update the timer the next time you change your connector settings.

• Timer on Jira Boards
  • Minimum 60 minutes
  • Maximum 1440 mins
• Timer on Jira Issues
  • Minimum 3 minutes
  • Maximum 120 minutes
• Timer on continuous push to Jira
  • Minimum 1 minute
  • Maximum 120 minutes

Most Jira Align instances have settings for issues and continuous push within these ranges already, but we've noticed multiple Jira board settings below the minimum. This controls the sync of recently created or updated Jira boards, sprints, and fix versions, but requires a significant number of API calls, and can slow overall sync times. While working with users who had large data sets, we saw that an increase in the board timer setting reduced sync cycle times by as much as 25%.

Jira connector: AND field now required

When setting up a JQL query on the Jira Integration tab in Jira Settings, the AND field is now required. 

API 2.0: Snapshots endpoints updated

The GET, POST, PUT, and PATCH Snapshot endpoints have been extended to include Funding Levels and Work Structure fields.

API 2.0: Release endpoints updated

The GET, POST and PUT Release endpoints have been extended to include Program Allotment and Program fields.

Default program increment image updated for roadmaps

We’ve updated the default image that displays at the top of each program increment when using the Program Increment view of the Roadmaps page. This change updates the default to Atlassian branding and corrects some load failures we identified in our performance logs.

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.