Release notes for 10.114.X

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

• Enhancements and Features
• Defect Fixes

Enhancements and Features

These features for 10.114 were released to environments on the continuous release track on November 18, 2022, in version 10.114.0. The features will then be released to environments on the bundled release track on December 2, 2022, in version 10.114.2:

.NET 6 now required 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. 

Jira connector: Bidirectional t-shirt sync

We’ve added the ability to sync t-shirt size estimates bidirectionally between Jira Software and Jira Align. This change provides more options and consistency with other mapped Jira fields. Previously, t-shirt estimates only synced in one direction, from Jira Align to Jira.

To enable bidirectional sync, change the Sync direction dropdown found at Admin > Jira Settings > Jira Setup > T-Shirt from Jira Align to Jira sync to Bidirectional sync. Before doing so, please review the warning and example about unintentional overwrites at the bottom of this section. Bidirectional sync will be the default setting for any newly-created Jira connectors. Existing connectors will continue using the Jira Align to Jira sync direction until manually changed.

A third option for sync direction, Jira to Jira Align sync, is coming soon.

We’ve also added the ability to map Jira Align’s No estimate value for t-shirt estimates with a custom Jira value.

You have two options for using this mapping:

• If you would like blank values in Jira to represent an unestimated t-shirt size, leave the mapping for the No estimate size blank in the settings window.
• If you would like to use a value such as “not estimated”, etc, for representing unestimated items, you may enter that value for the No Estimate size in the settings window.
  • Note that when you map a Jira custom value to the No estimate Jira Align value, blank entries in the Jira field will be ignored during sync, to prevent your Jira Align value from being changed.

Important! If you’re enabling bidirectional t-shirt sync for the first time, you must take care to avoid an accidental overwrite that could occur when Jira data is synced to Jira Align. This situation may be rare, but it could occur if Jira t-shirt size estimates have been set as blank, and the corresponding Jira Align features have not been updated. Consider this example:

Jira connector: Restricted Process Step and State fields when synced with Jira’s Done status

As part of resolving a reported defect, JIRAALIGN-3705, we’ve made a change to available selections in the State and Process Step fields for features and stories that are synced with Jira. When a synced Jira Align work item is updated with a state or process step value that is mapped to Jira’s Done status, you will only be able to select different values that are also mapped to Jira’s Done status. This is because the Jira connector can't remove the resolution of a Jira issue. To remove a Jira resolution, change the status inside Jira.

Jira connector: Changes to Default User settings

To help administrators avoid potential issues such as typos when entering a value, the Default User field found at Admin > Jira Settings > Jira Setup has been changed from a text field to a dropdown. You can search inside the field to locate the account you want to use as the default user. Additionally, to prevent sync issues, the field is now required.

Jira connector: Enforcing 1:1 mapping between Jira and Jira Align sprints

To prevent sprint mapping issues, we’ve removed the ability to manually map multiple Jira sprints to a single Jira Align sprint on the Admin > Jira Management > Jira Sprints settings page. Jira Align sprints that are already mapped to a Jira sprint will not be selectable and will display an error message.

Jira connector: Renamed settings and options

We’ve made some updates to the names and tooltips inside Jira connector settings to help administrators better understand the behavior of each setting:

Settings found at Admin > Jira Settings > Jira Setup

Settings found in the Team-managed project settings tab (Admin > Jira Settings > Manage Projects > [Name of project])

Sync dropdowns (Admin > Jira Settings > Jira Setup)

We’ve also changed the values found in dropdowns that control sync direction to be more clear. Instead of Yes and No, administrators can select either Bidirectional sync or Jira to Jira Align sync for the following settings:

• Permission to Edit Initiative Name
• Permission to Edit Epic Name
• Enable Epic Sync
• Enable Feature Sync
• Enable Story Sync
• Enable Defect Sync
• Enable Task Sync
• Enable Epic State Sync
• Enable Feature State Sync
• Enable Story State Sync
• Enable Defect State Sync
• Allow Jira Align to create Jira issue web links

Administrators can select either Bidirectional sync or Not synced for these settings:

• Allow release vehicles to sync with Jira Fix Versions
• Enable Rank Sync

API 2.0 support for the DELETE method

We’ve added API 2.0 support for the DELETE method for the following items:

• Cities
• Customers
• Goals
• Ideas
• Products
• Regions
• Risks
• Snapshots
• Sprints

Objectives tree (new experience): Status counts

We’ve added status counts to the four quick-filter status cards displayed at the top of the new objectives tree experience.

These counts show the total number of objectives or milestones with a specific status. The counts are tied to the selections made in the Configuration bar and page-level filters. 

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.