# Jira DC to Azure Dev Ops not delivering data and no errors Shown

**URL:** <https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840>\
**Category:** General Questions\
**Created:** [October 15, 2025, 8:07pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840 "2025-10-15T20:07:40Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Honduras74](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@Honduras74](https://community.exalate.com/u/Honduras74)\
**Post date:** [October 15, 2025, 8:07pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/1 "2025-10-15T20:07:41Z")

</div>

When Synching a multiline custom field in Jira Called “Acceptance Criteria” to ADO System Field “Acceptance Criteria” There are no errors shown but there is no data being updated in the ADO side for this field.

Jira outgoing synch Code:  
def acCf = issue.customFields.“Acceptance Criteria”

if (acCf && acCf.value?.trim()) {

// IMPORTANT: send the CF object, not the String

replica.customFields.“Acceptance Criteria” = acCf

} else {

// Keep payload clean if empty

replica.customFields.remove(“Acceptance Criteria”)

}

ADO Incoming Synch

// — ADO INCOMING: map to system Acceptance Criteria (HTML) —  
// Correct reference name (case-sensitive):  
def AC\_REF = “Microsoft.VSTS.Common.AcceptanceCriteria”

// Be defensive: ensure the map exists  
workItem.fields = workItem.fields ?: [:]

// Pull text from payload  
def acText = (replica.customFields.“Acceptance Criteria”?.value ?: “”) as String  
exLogger.info(“[AC IN] raw=‘${acText.take(200)}’ length=${acText.size()}”)

// Quick HTML safety + newline preservation for ADO HTML control  
def htmlFromPlain = { String s →   
if (!s) return null  
def esc = s.replace(“&”,“&”).replace(“\<”,“\<”).replace(“\>”,“\>”)  
// Use   
 instead of

```
so it blends with existing ADO field styling
esc.replace(“\r\n”, “\n”).replace(“\n”,“
”)
}

// 1) Write Acceptance Criteria if non-empty  
def html = htmlFromPlain(acText)  
if (html) {  
workItem.fields[AC\_REF] = html  
exLogger.info(“[AC IN] wrote AcceptanceCriteria (${html.size()} chars)”)  
} else {  
exLogger.info(“[AC IN] nothing to write into AcceptanceCriteria (empty)”)  
}
```

---

<div class="post-metadata">

**Author:** ![Aida](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/aida/32/580_2.png) [@Aida](https://community.exalate.com/u/Aida)\
**Post date:** [October 15, 2025, 8:08pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/2 "2025-10-15T20:08:02Z")

</div>

It sounds like you’re running into a classic scenario where a Jira custom field (“Acceptance Criteria”) isn’t syncing to the Azure DevOps system field, and there are no errors to help debug. Here are some key points and troubleshooting steps based on Exalate documentation:

1. **Custom Field Visibility in Jira** :  
Exalate requires the custom field to be present on the Issue View screen in Jira. If it’s not, the field won’t sync—even though you won’t see any errors. Double-check that your “Acceptance Criteria” custom field is added to the relevant screen in Jira.  
[See details here](https://docs.exalate.com/docs/custom-fields-dont-sync)

2. **Field Name Overlap** :  
Jira allows custom fields to have the same name as system fields, which can cause confusion. Make sure you’re referencing the correct field in your sync rules.  
[More info here](https://docs.exalate.com/docs/overlap-between-custom-fields-and-system-fields)

3. **Sync Rule Structure** :  
For syncing a Jira custom field to an Azure DevOps system field, your outgoing and incoming sync rules should look like this:

4. **Field Type Handling** :  
Azure DevOps “Acceptance Criteria” is a multi-line text (HTML) field. Ensure your conversion to HTML is working as expected, and that you’re not sending an empty string.

5. **No Errors, No Data** :  
If you see no errors and no data, it’s almost always a field mapping or visibility issue. Double-check the field names, their presence on screens, and that your sync rules are referencing the correct fields.

If you’ve confirmed all the above and it’s still not working, try logging the value of `issue.customFields."Acceptance Criteria"` in your Jira outgoing sync to ensure it’s being picked up as expected.

Let me know if you need more specific troubleshooting steps!

---

<div class="post-metadata">

**Author:** ![Honduras74](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@Honduras74](https://community.exalate.com/u/Honduras74)\
**Post date:** [October 15, 2025, 9:00pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/3 "2025-10-15T21:00:34Z")

</div>

The Value is being picked up By Jira outgoing Synch.

2025-10-15 15:38:42,749-0500 http-nio-8080-exec-14 url: /rest/issuehub/4.0/errors/connections/29/resolveAll; user: \* **DEBUG** 938x98190x1 1astc08 10.221.13.160,10.222.96.1 /rest/issuehub/4.0/errors/connections/29/resolveAll [Shackles] \*\*\*\*[AC OUT] present=true id=11800 value='

Acceptance CriteriB

---

<div class="post-metadata">

**Author:** ![Ariel\_Aguilar](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/ariel_aguilar/32/341_2.png) [@Ariel\_Aguilar](https://community.exalate.com/u/Ariel_Aguilar)\
**Post date:** [October 28, 2025, 3:13pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/4 "2025-10-28T15:13:19Z")

</div>

Hi @Honduras74,

Can you confirm if the value from Jira is flowing to ADO? If it is, are you able to logging the value in your ADO incoming sync?

Kind regards,

Ariel

---

<div class="post-metadata">

**Author:** ![Honduras74](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@Honduras74](https://community.exalate.com/u/Honduras74)\
**Post date:** [October 28, 2025, 3:50pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/5 "2025-10-28T15:50:15Z")

</div>

Here are both Jira Outgoing and ADO Incoming scripts.  
Jira values are flowing to ADO: confirmed. ADO is receiving the values: confirmed. No errors are shown anywhere, ADO still not adding or updating any of the values. It does create the Story but does not add any of the fields.

[ADO-Full-Incomming-Clean.txt](https://community.exalate.com/uploads/short-url/9dueYDyRMCqxIgEPLH8kISecdHq.txt) (4.6 KB)

[JiraOutgoingSynch-clean full.txt](https://community.exalate.com/uploads/short-url/bnKVUCi1pRLs2cyYwV1b6ViVIZh.txt) (5.7 KB)

---

<div class="post-metadata">

**Author:** ![Honduras74](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@Honduras74](https://community.exalate.com/u/Honduras74)\
**Post date:** [October 28, 2025, 3:50pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/6 "2025-10-28T15:50:56Z")

</div>

Here you go @Ariel_Aguilar

---

<div class="post-metadata">

**Author:** ![Ariel\_Aguilar](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/ariel_aguilar/32/341_2.png) [@Ariel\_Aguilar](https://community.exalate.com/u/Ariel_Aguilar)\
**Post date:** [October 28, 2025, 4:03pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/7 "2025-10-28T16:03:48Z")

</div>

Hi @Honduras74,

Have you tried to pass the value without the html conversion?

Kind regards,

Ariel

---

<div class="post-metadata">

**Author:** ![Honduras74](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@Honduras74](https://community.exalate.com/u/Honduras74)\
**Post date:** [October 28, 2025, 6:13pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/8 "2025-10-28T18:13:36Z")

</div>

@Ariel_Aguilar That’s how the original script started, added the HTML conversion later thinking it was the reason it wasn’t passing the data. The thing is none of the other fields are working, no matter what data type they are.

---

<div class="post-metadata">

**Author:** ![Ariel\_Aguilar](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/ariel_aguilar/32/341_2.png) [@Ariel\_Aguilar](https://community.exalate.com/u/Ariel_Aguilar)\
**Post date:** [October 28, 2025, 6:20pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/9 "2025-10-28T18:20:36Z")

</div>

Can you try to do something simple in the incoming script to check if it works:

```auto
workItem."Microsoft.VSTS.Common.AcceptanceCriteria" = replica.customFields."Acceptance Criteria".value

```

Let me know if this works for you.

---

<div class="post-metadata">

**Author:** ![Honduras74](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@Honduras74](https://community.exalate.com/u/Honduras74)\
**Post date:** [October 29, 2025, 4:53pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/10 "2025-10-29T16:53:45Z")

</div>

@Ariel_Aguilar That absolutely worked!

---

<div class="post-metadata">

**Author:** ![Honduras74](https://avatars.discourse-cdn.com/v4/letter/h/9fc29f/32.png) [@Honduras74](https://community.exalate.com/u/Honduras74)\
**Post date:** [October 29, 2025, 6:34pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/11 "2025-10-29T18:34:23Z")

</div>

@Ariel_Aguilar would this approach work for system. Fields?

---

<div class="post-metadata">

**Author:** ![Ariel\_Aguilar](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/ariel_aguilar/32/341_2.png) [@Ariel\_Aguilar](https://community.exalate.com/u/Ariel_Aguilar)\
**Post date:** [October 29, 2025, 10:08pm UTC](https://community.exalate.com/t/jira-dc-to-azure-dev-ops-not-delivering-data-and-no-errors-shown/6840/12 "2025-10-29T22:08:47Z")

</div>

Glad to hear that worked! Yes, the same approach should also be applied to the system fields.

Kind regards,

Ariel
