The Atlassian Jira Align team is pleased to announce Jira Align v.10.109.
Enhancements and Features
These features for 10.109 were released to environments on the continuous release track on July 1, 2022, in version 10.109.0. The features will then be released to environments on the bundled release track on July 15, 2022, in version 10.109.2:
Azure DevOps connector: Automatic sprint assignment and allocations
Users are now assigned to sprints in Jira Align when the user is added as the assignee of a story, defect, or child task that is assigned to a team and a sprint.
Users will receive an allocation of 100% for each sprint. If a user is a member of two or more sprints within one anchor date, their allocation of 100% will be equally distributed across all of these sprints.
For example, if there are three sprints, the allocation for each team sprint will be calculated as:
100% / (3 sprints user is added to within the anchor date) = 33%
When a user is added to a Kanban team, allocations are re-calculated to be equally distributed across all Kanban teams and team sprints within the present anchor date range, for a total of 100%.
Azure DevOps connector: Field defaults
For stories, features, and bugs where the sync direction is bidirectional, you can now configure default values for Azure DevOps fields. Default values can be used to prevent sync issues with required fields in Azure DevOps when the corresponding fields are not required in Jira Align. If there’s no value already set on the field in Azure DevOps, and no value supplied from Jira Align, the connector will set the Azure DevOps field to the default value.
Azure DevOps connector: Limit ability to move synced work items between programs in Jira Align
In order to prevent any possible sync issues that may occur when a user moves synced work items between programs or Azure DevOps area paths in Jira Align, it is not allowed to change program assignment (primary program for features). If users need to move a work item, change the area path assignment in Azure DevOps and changes will sync to Jira Align.
Updates to Jira connector logic that auto-calculates and syncs estimates
In a previous announcement, we highlighted changes to the sync behavior of estimates between Jira and Jira Align to prevent unintentional overwrites from occurring.
When a Jira Align portfolio is set to use point estimates:
- Jira Align will no longer sync a T-shirt size estimate to Jira Software, even if a custom field for T-shirt size is mapped in connector settings.
- If the connector is set to sync points to Align, a points field must be configured in Jira Software. If this is not present, syncs from Jira will write a 0 into the points field in Jira Align.
When a Jira Align portfolio is set to use t-shirt size estimates:
- Points synced from Jira will not be converted into a T-shirt size in Jira Align. Any T-shirt estimates entered in Align prior to a sync will be retained.
- Converted point values in Jira Align (hidden in the database, but converted from an entered T-shirt size) will not sync to Jira.
- T-shirt sizes entered in Jira Align will continue to sync to Jira.
Note: The type of estimation system used is available as both a global and portfolio-specific setting. If a selection has not been made for a specific portfolio, the global setting is used.
In upcoming releases, we’ll be making additional changes to estimation sync behavior and connector settings to provide a better experience in the future.
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.
|JIRAALIGN-4159||Unable to use a PUT or PATCH call on Release to change the Status from the Archive status (i.e. 4) to any other status such as Done (i.e. 3)||10.109.0|
|JIRAALIGN-3190||ADO Connector: Incorrect Audit log entry||10.109.0|
|JIRAALIGN-3839||API: when an update is made to a User through the API, the audit logs shows changes not related to i||10.109.0|
|JIRAALIGN-3685||Why Does the Organization Structure Code exclude special characters?||10.109.0|
|JIRAALIGN-4156||Post Calls to Epics Endpoint Throws an Error If The Owner Field is Set as Required in JA||10.109.0|
|JIRAALIGN-4078||Refreshing the page on the Program Team or Team page gives a user the ability to edit team members when not possible before refreshing the page||10.109.0|
|JIRAALIGN-4150||Irrelevant error message while wrong data type was passed while running PUT request on Releases||10.109.0|
|JIRAALIGN-4063||Dependencies Grid: Filter on Capabilities is not returning any results.||10.109.0|
|JIRAALIGN-4192||Jira Connector - Consolidate User Error||10.109.0|
|JIRAALIGN-4193||REST API 2.0: Adding a link via PATCH or PUT is not working as expected||10.109.0|
|JIRAALIGN-4155||When importing stories, there is no error on the Import page, but the stories do not get imported||10.109.1|
|JIRAALIGN-4093||Anyone with Mind Map Enterprise Role can create work items from Mind Maps, ignoring other permissions||10.109.2|
|JIRAALIGN-4195||Ideation : Ideation Group's externally accessible URL remains active even though Make Public setting is switched off||10.109.2|
|JIRAALIGN-4234||Investment vs Spend report displaying "Slice" instead of Theme label for Accepted Spend chart||10.109.2|
Join the Atlassian Community!
The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.
Need to contact Jira Align Support? Please open a support request.