Currently, the Azure DevOps integration data mapping table for the section: Azure DevOps features become features in Jira Align shows that the Priority field is not part of the synchronization data.

Similar to what we can do with Jira Connector, having the possibility to map and synchronize bi-directionally the Priority data between Azure DevOps and Jira Align would be great.

To workaround the situation, you can use the following two options:

Workaround #1

Use the default field sync

Define the default synchronization (Jira Align to Azure DevOps) for the Priority field under the Azure DevOps Field Defaults section (as per the Configure and activate Azure DevOps integration help page):

10. For stories, features, and bugs where the sync direction is bidirectional, in the Azure DevOps Field Defaults (Jira Align to Azure DevOps) section, type the Azure DevOps Field you’d like to set a default value for. Then, set the Default Value. 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.

1. Add additional field default values by selecting the Add button. You can also delete field default values by clicking the X icon next to the mapping.

 
However, please note that the default value will * only be synchronized at creation time

• only be synchronized unidirectionally (Jira Align to Azure DevOps)

• not take into account (i.e. ignore) the Priority set at the Jira Align Feature level

Workaround #2

Custom field sync

Create and configure the mapping of a Jira Align custom field (i.e. custom single-select dropdown field) to sync with the ADO Priority field value. On the other hand, this option will not utilize the default Jira Align Priority.

This option will allow you to get the ADO priority information sync bi-directionally but this would not be on the Jira Align's default priority field, but rather a custom field.