# Azure DevOPS to Jira Cloud - Sync Acceptance Criteria

**URL:** <https://community.exalate.com/t/azure-devops-to-jira-cloud-sync-acceptance-criteria/4312>\
**Category:** General Questions\
**Tags:** azuredevops-jiraclou, migrated\_question\
**Created:** [November 4, 2024, 6:47am UTC](https://community.exalate.com/t/azure-devops-to-jira-cloud-sync-acceptance-criteria/4312 "2024-11-04T06:47:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 6:47am UTC](https://community.exalate.com/t/azure-devops-to-jira-cloud-sync-acceptance-criteria/4312/1 "2024-11-04T06:47:01Z")

</div>

_Originally asked by Charlie Schonken on 14 August 2020 [(original question)](https://oldcommunity.exalate.com/questions/11341462)_

* * *

Our client uses Azure DevOPS to log tickets, which are then sync’d to our JIRA service desk using Exalate.

In DevOPS, an outgoing sync has been defined for customfield

```auto
replica.customFields."Acceptance Criteria" = issue.customFields."Acceptance Criteria"  

```

In JIRA an Incoming sync has been defined for the customField as follows

```auto
issue.customFields."10500".value = replica.customFields."Acceptance Criteria"  

```

… however, nothing is populating in JIRA. The field is not updated at all.

We then changed it to …

```auto
issue.customFields."10500".value = replica.customFields."Acceptance Criteria"?:""  

```

… which then blanks the field in JIRA, so we definitely have the right JIRA field.

In discussion with Roman from support, we tried another variation …

```auto
replica.customFields."Acceptance Criteria" = workItem.customFields."Acceptance Criteria"  

```

and in the Incoming rule on Jira side

```auto
  
issue.customFields."10500".value = replica.customFields."Acceptance Criteria".value  
  
... this also did not work, and resulted in Sync errors.  
  
Support then came back to me saying ...

```

“I have asked around regarding your case. Acceptance Criteria field is not a custom field it is specific to User Story Type in Azure. This is not supported by exalate yet. I need need to check with my Canadian colleagues on is there a chance that this will be supported in the future and will get back to you later in the day.”

* * *

---

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 4, 2024, 6:47am UTC](https://community.exalate.com/t/azure-devops-to-jira-cloud-sync-acceptance-criteria/4312/2 "2024-11-04T06:47:02Z")

</div>

_Answer by Roman on 14 August 2020_

Hey Charlie Schonken

Acceptance Criteria is a HTML field that is specific for User Type Story issue type on Azure side. In order to sync it you would need to send it from the Azure side:

Outgoing sync:

```auto
replica.AcceptanceCriteria = nodeHelper.stripHtml(workItem."Microsoft.VSTS.Common.AcceptanceCriteria")

```

Incoming on the Jira Cloud side should be

```auto

issue.customFields."10500".value = replica.AcceptanceCriteria

```

```auto
  
  
Let me know how it goes   
  

```

* * *

#### Comments:

> **Charlie Schonken commented on 14 August 2020**
>
> > Perfect! Works like a bomb.

---

<div class="post-metadata">

**Author:** ![xl8bot](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/xl8bot/32/324_2.png) [@xl8bot](https://community.exalate.com/u/xl8bot)\
**Post date:** [November 6, 2024, 6:47am UTC](https://community.exalate.com/t/azure-devops-to-jira-cloud-sync-acceptance-criteria/4312/3 "2024-11-06T06:47:27Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.