Release notes for 10.117.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 previously reported features, 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 section below for details:

Previously reported features and defect fixes

Changes to the API 2.0 were previously detailed in these notes, but due to deployment issues, were not released to environments in version 10.117.0. These changes will ship in the near future and will be included in an upcoming Release Notes article:

  • GET, POST, PUT, and PATCH support for capability acceptance criteria
  • GET and POST support for epic acceptance criteria
  • POST, PUT, and PATCH support for epic links
  • Copy endpoints for capabilities and features
  • PATCH support for releases
  • PUT and PATCH support for value streams
  • Audit log endpoints for value streams, products, customers, and cities

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

Enhancements and Features

These features for 10.117 were released to environments on the continuous release track on February 10, 2023, in version 10.117.0. The features will then be released to environments on the bundled release track on March 3, 2023, in version 10.117.3:

Enhanced Default Sync User setting dropdown in Azure DevOps connector

The dropdown control has been changed to fix performance issues that took place when the list contained thousands of users.


Jira Connector: modernized state mapping modal

We updated the design of the Jira Align to Jira state mapping modal (Administration > Jira Settings > Manage Projects > State Mapping link). The content on the modal was updated, the process step toggle was moved to the top of the page as it controls all work item types, and now all changes to mappings will save automatically. The logic behind the mapping modal has not changed and existing mappings have not been modified.


When a connector isn’t configured to sync from Jira Align to Jira, an empty state message will prompt you to update your issue type mappings or sync settings.


We've also updated the experience when adding a new project to the connector, to ensure data quality and that mappings are valid. Once a project is added to the Manage Projects tab, we will check:

  1. That the project key is valid and we can successfully connect to it.
  2. The type of project being added — team-managed or company-managed. 
  3. The statuses associated with the project. 

Prior to these checks during initial sync, invalid keys, project types, and statuses could be mapped, causing sync issues. Note that a newly-added project will not display the State Mapping link at the right side of the project row until the initial sync and checks are completed. The sync will run according to your Timer for Jira boards, sprints, and fix versions setting. You can run a custom JQL query to immediately run this sync between Jira and Jira Align.

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-3131 Jira Connector: Stories for Status Mapping after Accepted moving to additional status/states 10.117.0
JIRAALIGN-3945 Already resolved story in Jira when synced, returns wrong 'State' via API 10.117.0
JIRAALIGN-4005 Team Dependency Map – after refreshing the page, Done option is OFF in Quick Filter 10.117.0
JIRAALIGN-4294 Performance: Live Roadmap may take an unacceptable amount of time to load 10.117.0
JIRAALIGN-4318 Epic Grid: Customer column sorting 10.117.0
JIRAALIGN-4441 Large quantity of Features causes Roadmap interaction to slow down/hang 10.117.0
JIRAALIGN-4548 Live Roadmap is not loading the grid 10.117.0
JIRAALIGN-4569 Permission toggle is not showing Terminology change 10.117.0
JIRAALIGN-4575 When Non-SA Users Try to Add Release Vehicle to a Story in Jira Align, it clears out the Process Step 10.117.0
JIRAALIGN-4637 Renaming a persona or role in Epic Personas results in a duplicate name/role. 10.117.0
JIRAALIGN-4675 Intake Form: changes to case development custom fields orders don't work correctly 10.117.0
JIRAALIGN-4739 Unable to Save/create new ADO in New Instance 10.117.1
JIRAALIGN-4499 Product field is not searching item in Feature screen 10.117.2
JIRAALIGN-4627 Theme Backlog: Themes from different Portfolios are displayed if Portfolio and Release are selected in Configuration bar and Program Increment is assigned to Programs from multiple Portfolios 10.117.2
JIRAALIGN-4684 Dependency: error 500 is thrown when rejecting a Dependency to a Program without Committed Date 10.117.2
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.