Release Notes for 10.105.X


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

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

Enhancements and Features

These features for 10.105 were released to environments on the continuous release track on February 4, 2022, in version 10.105.0. The features will then be released to environments on the bundled release track on February 18, 2022, in version 10.105.2:

Jira Connector: Rest API PAT authentication

Jira Server and Data Center customers can now use a Personal Authentication Token (PAT) to authenticate the Jira API. On the Jira Settings page, selecting a connector in the Connector dropdown, then selecting Jira Connectors brings up a Manage Jira Connectors modal with all the needed configuration settings.


PAT Authentication is now included in the Authentication Type options for the Jira connector. To set up PAT authentication, select PAT Authentication as the authentication type, then type the Jira PAT in the corresponding field that displays.

In the scope of these changes, we’ve also simplified the UI for the info icon next to the Authentication Type field. Now, instead of several separate links, this link leads to authentication types information inside our Jira Integration Setup article.

Finally, we’ve improved the Test connectivity information at the bottom of the modal. The link text has been changed to Test connecting to /rest/api/2/serverinfo for better guidance about the exact type of connectivity that is being tested when selecting this link.

Status Reports enhancement

We’ve improved Status Reports pages by linking the colored bars displayed in the Progress column to global settings.

Previously, these colors were hard-coded, and in-progress work items always displayed an orange color, which is sometimes associated with risks or delays. When the report was shown to upper management, stakeholders would often think that everything was in a state of high risk, while in fact, the work was ongoing.

Now, Progress colors for epics, stand-alone features, and capabilities are tied to global color settings, which can be configured according to your preferences. Global color settings can be found at Administration > Platform > General.


API 2.0: Custom field support for themes, capabilities, stories, and objectives

The API 2.0 has been updated to support multiple operations with custom fields. The following actions are now enabled:

  • Themes, capabilities, stories, and objectives: Use GET to collect all custom field metadata through the /{id}/editmeta URL:

    • Example: GET /rest/api/2/stories/123/editmeta

      This step is necessary to understand what custom field values currently exist, before using POST, PUT, or PATCH to modify them.

  • Themes, capabilities, stories, and objectives: 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

API 2.0: Links support

You may now perform POST, PUT, and PATCH operations against the Links section found within Details panels for epics, features, and stories.

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-3866 Capacity Planning Table returns totals as 0 value 10.105.0
JIRAALIGN-3863 Features grid - Business Driver field shows 'n/a' as the default value 10.105.0
JIRAALIGN-1574 Jira Connector doesn't update the PI to Unassigned in JA when the Fix Version was removed from item in Jira 10.105.0
JIRAALIGN-3837 Validation for required case development custom fields is not triggered after hitting Save or Save&Close on Epics 10.105.0
JIRAALIGN-3687 Theme: when creating a Theme without a Program, an error is thrown and it disappear from the Grid 10.105.0
JIRAALIGN-3868 Date timestamp of changes in state are not correctly captured - wrong timestamp 10.105.0
JIRAALIGN-2245 WSJF definition on the 'Why?' page should be corrected 10.105.0
JIRAALIGN-2198 Backlog: Time in Process Step/Value Stream displays 0 when the Process step was set on initial creation 10.105.0
JIRAALIGN-1941 Jira Connector: Synced Feature or Story reinstated by connector after canceling on Jira Align when using Process Step mapping for Jira Project 10.105.0
JIRAALIGN-3217 Strategic Driver Allocation Report showing Unassigned in error 10.105.0
JIRAALIGN-1577 Program Room: Incorrect Label for the 'Points' and 'Estimate' columns/Issue with TW to MW conversion 10.105.0
JIRAALIGN-1554 Program Board: Dependencies that are committed to within feature/team target completion causes red planning issue 10.105.0
JIRAALIGN-3847 Roadmap - Missing Epics in RoadMap once compared to Epic Grid 10.105.2
JIRAALIGN-3944 Null points will clear JA estimation when synced 10.105.2
JIRAALIGN-3950 Irrelevant Development tasks are added to Kanban boards and expanding tasks in stories slide-out panel is throwing an error 10.105.2
JIRAALIGN-3957 API 2.0 : Milestones: Making a GET call towards Milestones endpoint results in HTTP 500 10.105.2
N/A API 2.0: Milestones/Objectives PATCH for Custom Fields fails 10.105.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.