Release Notes for 10.107.X


The old navigation will be removed from Jira Align in early 2024.
Learn more about the upcoming changes

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 Beginning removal of operational process flows section below for details. 

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

Enhancements and Features

These features for 10.107 were released to environments on the continuous release track on April 22, 2022, in version 10.107.0. The features will then be released to environments on the bundled release track on May 6, 2022, in version 10.107.2:

Azure DevOps connector: Select a default role for users created by the connector

On the General tab of the Azure DevOps connector slideout, you can now choose the system role for users created by the connector with the Default Jira Align system role for ADO users setting. Changing this setting won't automatically change the role of existing users, only those created by the connector going forward.

API 2.0: Custom field support for defects and tasks

The API 2.0 has been updated to support multiple operations with custom fields. You can now perform these actions:

  • Defects and tasks: Use GET to collect all custom field metadata through the /{id}/editmeta URL:
    • Example: GET /rest/api/2/defects/123/editmeta
      This step is necessary to understand which custom field values currently exist, before using POST, PUT, or PATCH to modify them.
  • Defects and tasks: Add and modify values for existing custom fields managed from Details Panels Settings — POST, PUT, and PATCH.

    • Custom Text Input

    • Custom Text Area

    • Custom Dropdown

    • Custom Multi Dropdown

  • Note: Custom Fields are only returned as part of the GET to specific work items. They will not be included as part of queries (i.e. using $filter operations) or other operations. For example, GET /rest/api/2/defects/123 will return custom fields, but GET /rest/api/2/defects/?filter=id eq 123 will not.

API 2.0: Dynamic validation

We implemented the dynamic required fields validation for all the default fields tied to the Details Panels Settings page, so the API validation mirrors the validation in the UI.

You can also get information on whether a field is required with the endpoint/id/editmeta request. This may result in a change of behavior if your API workflow did not take into account required fields properly.

Upcoming changes to API 2.0: Removal of old fields from Defect, Task, and Theme objects

As we roll out our new support of custom fields across all supported work items, we will continue our efforts in ensuring consistency and usability for API usage. In that respect, we will be removing the usage of old custom fields for the Defect, Task, and Theme objects. Removal will occur no earlier than 10.109.0.

In version 10.109.0, we will remove these fields from DefectDto, TaskDto and ThemeDto:

  • ctext1
  • ctext2
  • carea1
  • cdrop1
  • cdrop2
  • cdrop3
  • cdrop4
  • cdrop5

Please update any workflows that may use the removed fields and move to the new custom fields workflow using the customFields field.

Additional spend details on features

We’ve added the Progression of spend section to the Spend tab of feature Details panels. This lets you quickly see financial values for a feature parented by an epic or capability. Previously, only stand-alone features displayed this section in Details panels. Select either value in the section to open the Estimated Spend or Accepted Spend panel, where you can see more info on how the value is calculated.


CSV exports for dependencies

You now have the ability to export a list of dependencies in .csv format. This replaces the previous file format of .xls. You can export from the Dependencies grid page by selecting the More Actions menu and then selecting Export All Dependencies or Export Action Required Dependencies.


Beginning removal of operational process flows

We’ve begun the process of removing operational process flows and operational process steps from the platform, due to low usage. While we initially intended to remove all elements in an upcoming release, some changes were deployed early.

In version 10.107.0, the Operational Step field has been removed from Details panels for themes, epics, capabilities, features, and stories.

Fields related to process flows and steps have also been updated in the API 2.0:

  • developmentalStepId changed to processStepId
  • operationalStepId was removed

All remaining references to operational type process flows and operational process steps will be removed from administration settings, Details panels settings, filters, and reports in a future release.

Consolidated process flow fields in Details panels

We’ve updated the experience inside of Details panels when a work item is associated with multiple program process flows. Now, when more than one program with a unique process flow is associated with a theme, epic, capability, or feature, the Process Step field from the primary program’s process flow will display. Selecting the + Show More link will display the remaining Process Step fields from other programs in alphabetical order, using the program’s name.


Corrected logic for Work Tree > Strategy View

The Strategy View of the Work Tree page has been updated to resolve an issue when moving from another view that supported the Narrow to Program and PI toggle. After enabling the toggle and changing the view to Strategy, the list of work items displayed was incorrect. Now, the view shows the same data regardless of the toggle selection inside other views. We’ve also updated the view’s info message confirming this behavior.


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.

Key Summary Release Version
JIRAALIGN-3198 The @ in Discussions doesn't work correctly 10.107.0
JIRAALIGN-4027 API 2.0 - When running a GET against a user the teams are not ordered so a Patch does not have consistent behavior 10.107.0
JIRAALIGN-1033 [JIRAALIGN-1033] FEATURE SPLIT - Duplicate split records created with duplicate Jira ID and different PIs 10.107.0
JIRAALIGN-2020 [JIRAALIGN-2020] Program Board: Target Dates for Stories are handled incorrectly when using dd/mm/yyyy date format 10.107.0
JIRAALIGN-1964 Epic Planning chart - label for red line on chart is incorrect 10.107.0
JIRAALIGN-3225 ADO Connector - syncing a new ADO user into JA gives them too high security privileges 10.107.0
JIRAALIGN-3563 Theme: Process Step field don't appear on the creation panel of a Theme 10.107.0
JIRAALIGN-3271 Backlog: for Capabilities when clicking Unassigned Backlog nothing is shown if Tier 1 has the Portfolio selected 10.107.0
JIRAALIGN-3998 RestAPI: Add Patch request for Epic links doesn't work as expected 10.107.0
JIRAALIGN-4031 Updating Objective status via PATCH API call adds Audit Log entry for Category instead of Status 10.107.0
JIRAALIGN-3893 API - PATCH a target Sync Sprint to a Kanban Team Objective generate duplicates in Team Room, Program Room and Program board. 10.107.0
JIRAALIGN-3840 API: User endpoint doesn't the update of an email with e a different case 10.107.0
JIRAALIGN-3930 Enterprise Insights: [FK User Modified By ID] missing in export_dw 10.107.0
JIRAALIGN-3913 API 2.0: Epic custom field update through PATCH doesn't record an entry on the Audit Logs 10.107.0
JIRAALIGN-3864 Features : Tags : Auto complete is not working 10.107.0
JIRAALIGN-3889 Team Sprints: Duplicate Members are added to the team sprint by the Jira Connector sync 10.107.0
JIRAALIGN-3966 Features slide-out panel throws whoops error when the product associated to the feature is set to itself as a parent product 10.107.0
JIRAALIGN-3498 Last 30 days and 3 months Date Range in Administration > Logs > Changes show no results when browser Language settings are set to EN-AU or EN-UK 10.107.0
JIRAALIGN-3949 Jira Connector: After renaming a Team, JA will not allow a new board to be added with the old name 10.107.0
JIRAALIGN-2771 API 2.0: /align/api/2/Iterations : Terminology label is displayed in Audit Log when creating Sprints via POST method 10.107.0
JIRAALIGN-3114 [JIRAALIGN-3114] Time Entry: Standard/Flexible Holidays for certain date tied to the entire Region don't show up on Time Entry page 10.107.0
JIRAALIGN-3850 Remove Feature Owner field inconsistencies between WEB UI and REST API 10.107.0
JIRAALIGN-2973 EPIC -> Work-Item links -> Predecessor, Successor dropdown loading issue 10.107.0
JIRAALIGN-3759 EI: Defect Attachment table, Test Attachment Table & Risk Attachment table are empty 10.107.0
JIRAALIGN-3928 Program Tracking report: Multi-team dependencies not rendered in a usable fashion in the UX 10.107.0
JIRAALIGN-3625 API 2.0: After an update an Epic through the UI, updates through the API will fail if a Theme is not provided 10.107.0
JIRAALIGN-3887 Performance: SQL Query timeout when editing and saving work items 10.107.0
JIRAALIGN-2986 Error creating Themes without Program 10.107.0
JIRAALIGN-2893 Developmental Step is not logged on Audit Log when creating a Feature 10.107.0
JIRAALIGN-3982 API 2.0: Executing PUT/PATCH call is multiplying by the wrong pivot field 10.107.0
JIRAALIGN-4076 Roadmap group by Objectives does not work for features 10.107.2
JIRAALIGN-3994 The Roadmap filter is not always retrieving all available items with solution filter in the tier1 configuration 10.107.3
Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

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.