# Script Library

**URL:** https://community.exalate.com/c/script-library/10.md

[Latest](https://community.exalate.com/latest.md) · [Categories](https://community.exalate.com/categories.md) · [Tags](https://community.exalate.com/tags.md)

---

## [About the Script Library category](https://community.exalate.com/t/about-the-script-library-category/5754)

<div class="topic-metadata">

**Author:** [@Majid](https://community.exalate.com/u/Majid)\
**Replies:** 0\
**Last updated:** [November 15, 2024, 6:03am UTC](https://community.exalate.com/t/about-the-script-library-category/5754 "2024-11-15T06:03:53Z")

</div>

Reusable synchronization scripts! Use this category to share, explore, and discuss scripts used with Exalate across supported platforms. Whether you’re building a custom sync script, troubleshooting a script, or lookin…

---

## [Sync Jira Sub-tasks to Azure DevOps as Parent–Child Work Items](https://community.exalate.com/t/sync-jira-sub-tasks-to-azure-devops-as-parent-child-work-items/8339)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [August 28, 2026, 10:12pm UTC](https://community.exalate.com/t/sync-jira-sub-tasks-to-azure-devops-as-parent-child-work-items/8339 "2026-08-28T22:12:51Z")

</div>

This script allows you to preserve the Jira parent/sub-task hierarchy when synchronizing issues from Jira to Azure DevOps. For example: Jira Azure DevOps PROJ-100 Task → User Story…

---

## [Display Multiple Connected Issues in a Rich Text Field in Jira Cloud](https://community.exalate.com/t/display-multiple-connected-issues-in-a-rich-text-field-in-jira-cloud/8314)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [August 22, 2026, 12:59am UTC](https://community.exalate.com/t/display-multiple-connected-issues-in-a-rich-text-field-in-jira-cloud/8314 "2026-08-22T00:59:53Z")

</div>

This use case is designed for scenarios where a single Jira Cloud issue is connected to multiple remote tickets or issues. It allows you to display information from all those connected items, such as their key, summary, …

---

## [How to Synchronize Remote Entities to Zendesk Organizations](https://community.exalate.com/t/how-to-synchronize-remote-entities-to-zendesk-organizations/8313)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [August 21, 2026, 10:04pm UTC](https://community.exalate.com/t/how-to-synchronize-remote-entities-to-zendesk-organizations/8313 "2026-08-21T22:04:31Z")

</div>

This example shows how to create or update a Zendesk Organization based on an entity synchronized through Exalate. In this case, we are synchronizing a Salesforce Account → Zendesk Organization. The same approach can be…

---

## [How to Sync Zendesk Custom Statuses](https://community.exalate.com/t/how-to-sync-zendesk-custom-statuses/7811)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [March 13, 2026, 9:01pm UTC](https://community.exalate.com/t/how-to-sync-zendesk-custom-statuses/7811 "2026-03-13T21:01:54Z")

</div>

In Zendesk, setting the regular ticket status only updates the status category such as new, open, pending, hold, or solved. If your workflow relies on custom statuses, you must update the custom\_status\_id field instead. …

---

## [Exalate Error on Duplicate User Name, Despite Unique Email (Jira to Azure DevOps)](https://community.exalate.com/t/exalate-error-on-duplicate-user-name-despite-unique-email-jira-to-azure-devops/6937)

<div class="topic-metadata">

**Author:** [@Matthew\_Berzinskas](https://community.exalate.com/u/Matthew_Berzinskas)\
**Replies:** 3\
**Last updated:** [December 22, 2025, 6:16am UTC](https://community.exalate.com/t/exalate-error-on-duplicate-user-name-despite-unique-email-jira-to-azure-devops/6937 "2025-12-22T06:16:50Z")

</div>

Hello - we have a case where there are duplicate user names in our Azure Devops, for example: John Smith - john.smith@company.com John smith - john.smith2@coompany.com Situation: Jira is sending an email address: re…

---

## [Sync Azure DevOps History into a remote text field or comment](https://community.exalate.com/t/sync-azure-devops-history-into-a-remote-text-field-or-comment/7568)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [December 13, 2025, 2:18am UTC](https://community.exalate.com/t/sync-azure-devops-history-into-a-remote-text-field-or-comment/7568 "2025-12-13T02:18:01Z")

</div>

This script captures Azure DevOps (ADO) work item history and syncs a readable summary into Jira Cloud, preserving important change context that cannot be migrated natively. I have used Jira cloud as an example, but it …

---

## [Freshservice assets sync -\> remote instance text field](https://community.exalate.com/t/freshservice-assets-sync-remote-instance-text-field/6943)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [November 22, 2025, 1:32am UTC](https://community.exalate.com/t/freshservice-assets-sync-remote-instance-text-field/6943 "2025-11-22T01:32:41Z")

</div>

This script retrieves the Assets associated with a Freshservice ticket and adds their details into a Jira Cloud text field. In this example I’ve used Jira Cloud, but you can sync the Assets into a text field on all issue…

---

## [Freshservice Requested items -\> Remote instance text field](https://community.exalate.com/t/freshservice-requested-items-remote-instance-text-field/6942)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [November 22, 2025, 1:03am UTC](https://community.exalate.com/t/freshservice-requested-items-remote-instance-text-field/6942 "2025-11-22T01:03:28Z")

</div>

This script retrieves the Requested Items of a Freshservice Request (catalog items and their field values) and automatically adds them to the Jira Cloud issue description. In this example I’ve used Jira Cloud, but you ca…

---

## [Sync Worknotes from ServiceNow to Jira Cloud](https://community.exalate.com/t/sync-worknotes-from-servicenow-to-jira-cloud/6034)

<div class="topic-metadata">

**Author:** [@Sonal\_Otwani](https://community.exalate.com/u/Sonal_Otwani)\
**Replies:** 2\
**Last updated:** [May 31, 2025, 7:46am UTC](https://community.exalate.com/t/sync-worknotes-from-servicenow-to-jira-cloud/6034 "2025-05-31T07:46:18Z")

</div>

I have a connection from ServiceNow to Jira Cloud. However, when I view the comments in Jira Cloud, the formatting appears incorrect.

---

## [Force Update with ScriptRunner for Jira DC](https://community.exalate.com/t/force-update-with-scriptrunner-for-jira-dc/6311)

<div class="topic-metadata">

**Author:** [@Tomas\_Lalanne](https://community.exalate.com/u/Tomas_Lalanne)\
**Replies:** 0\
**Last updated:** [April 7, 2025, 11:50am UTC](https://community.exalate.com/t/force-update-with-scriptrunner-for-jira-dc/6311 "2025-04-07T11:50:09Z")

</div>

On this post we will have a Script that uses ScriptRunner tool We will have a custom Listener. that when an automation is done thru SR, it will force an UPDATE EVENT, that will send all the modifications. This force he…

---

## [How to perform a JQL search inside Jira DC incoming script](https://community.exalate.com/t/how-to-perform-a-jql-search-inside-jira-dc-incoming-script/6275)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [March 20, 2025, 9:57pm UTC](https://community.exalate.com/t/how-to-perform-a-jql-search-inside-jira-dc-incoming-script/6275 "2025-03-20T21:57:04Z")

</div>

This script demonstrates how to perform a Jira Query Language (JQL) search using the Jira DC (Data Center) incoming script, and return a list of issues based on specified criteria. JQL Query Creation: The script uses th…

---

## [How to update a Jira Cloud parent issue field via REST API](https://community.exalate.com/t/how-to-update-a-jira-cloud-parent-issue-field-via-rest-api/6176)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [February 4, 2025, 8:02pm UTC](https://community.exalate.com/t/how-to-update-a-jira-cloud-parent-issue-field-via-rest-api/6176 "2025-02-04T20:02:16Z")

</div>

This use case involves updating the parent field of a Jira issue during Exalate synchronization. Since Jira Cloud requires API-based updates for certain fields like parent , the script uses the Jira Cloud REST API to dyn…

---

## [How to Automatically Synchronize Linked Issues (Jira Cloud)](https://community.exalate.com/t/how-to-automatically-synchronize-linked-issues-jira-cloud/6148)

<div class="topic-metadata">

**Author:** [@Javier](https://community.exalate.com/u/Javier)\
**Replies:** 0\
**Last updated:** [January 24, 2025, 1:12am UTC](https://community.exalate.com/t/how-to-automatically-synchronize-linked-issues-jira-cloud/6148 "2025-01-24T01:12:48Z")

</div>

This script synchronizes linked issues in Jira Cloud using Exalate. It retrieves the issuelinks from an issue and automatically synchronizes each linked issue, whether there’s one or multiple. Script Overview Retrieve …

---

## [Azure Devops -\> Jira Service Management: Keep Synced Attachments internal and comment impersonation](https://community.exalate.com/t/azure-devops-jira-service-management-keep-synced-attachments-internal-and-comment-impersonation/5818)

<div class="topic-metadata">

**Author:** [@mathieu](https://community.exalate.com/u/mathieu)\
**Replies:** 0\
**Last updated:** [November 19, 2024, 4:29am UTC](https://community.exalate.com/t/azure-devops-jira-service-management-keep-synced-attachments-internal-and-comment-impersonation/5818 "2024-11-19T04:29:42Z")

</div>

Introduction Hello all, Picture this: You’ve successfully synced Azure DevOps and Jira Cloud, with a fully operational JSM project up and running. Now, suppose you come across a scenario where you’d prefer all attachm…

---

## [How to sync Tempo Worklogs between two Jira Cloud instances](https://community.exalate.com/t/how-to-sync-tempo-worklogs-between-two-jira-cloud-instances/5823)

<div class="topic-metadata">

**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Replies:** 0\
**Last updated:** [November 19, 2024, 6:14am UTC](https://community.exalate.com/t/how-to-sync-tempo-worklogs-between-two-jira-cloud-instances/5823 "2024-11-19T06:14:39Z")

</div>

Introduction I’m excited to present this tutorial, where we will explore the seamless synchronization of Tempo Worklogs between two Jira Cloud instances using Exalate. To set the stage, let’s consider a scenario where w…

---

## [How to sync SLA information from a Zendesk ticket to a Jira Issue?](https://community.exalate.com/t/how-to-sync-sla-information-from-a-zendesk-ticket-to-a-jira-issue/5821)

<div class="topic-metadata">

**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Replies:** 0\
**Last updated:** [November 19, 2024, 6:03am UTC](https://community.exalate.com/t/how-to-sync-sla-information-from-a-zendesk-ticket-to-a-jira-issue/5821 "2024-11-19T06:03:54Z")

</div>

A service level agreement, or SLA policy is an agreed upon measure of the response and resolution times that your support team delivers to your customers. For example, you can define an agreement where you respond to ur…

---

## [Jira -\> Azure Devops: Create new sprints in ADO that don't exist yet, with REST API and Exalate](https://community.exalate.com/t/jira-azure-devops-create-new-sprints-in-ado-that-dont-exist-yet-with-rest-api-and-exalate/5824)

<div class="topic-metadata">

**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Replies:** 0\
**Last updated:** [November 19, 2024, 6:19am UTC](https://community.exalate.com/t/jira-azure-devops-create-new-sprints-in-ado-that-dont-exist-yet-with-rest-api-and-exalate/5824 "2024-11-19T06:19:23Z")

</div>

Introduction Hello all, The scene: You have set up a succesful integration between Jira and Azure Devops. You want to integrate Sprints aswell. In Jira (any deployment), the sprints already exist, but in Azure Devops,…

---

## [Jira Cloud \<-\> Zendesk Sync comments and Description with formatting](https://community.exalate.com/t/jira-cloud-zendesk-sync-comments-and-description-with-formatting/5825)

<div class="topic-metadata">

**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Replies:** 0\
**Last updated:** [November 19, 2024, 6:28am UTC](https://community.exalate.com/t/jira-cloud-zendesk-sync-comments-and-description-with-formatting/5825 "2024-11-19T06:28:44Z")

</div>

Introduction Jira Cloud comment supports formatting like bold, italic, underline , colour fonts and many more. To sync this to Zendesk is not totally supported by Exalate. The reason being, Jira cloud is using Mark Up l…

---

## [Azure Devops -\> Jira On-Prem: Multi-level Issue Hierarchy](https://community.exalate.com/t/azure-devops-jira-on-prem-multi-level-issue-hierarchy/5817)

<div class="topic-metadata">

**Author:** [@mathieu](https://community.exalate.com/u/mathieu)\
**Replies:** 0\
**Last updated:** [November 18, 2024, 9:00pm UTC](https://community.exalate.com/t/azure-devops-jira-on-prem-multi-level-issue-hierarchy/5817 "2024-11-18T21:00:59Z")

</div>

The main requirement for this use case is to maintain the multi-level issue hierarchy while Exalating issues from Azure DevOps to Jira Server/DC. The relationship on Azure DevOps is Epic → Feature → Task, and this shoul…

---

## [Azure DevOps Convert wiki to HTML](https://community.exalate.com/t/azure-devops-convert-wiki-to-html/5975)

<div class="topic-metadata">

**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Replies:** 0\
**Last updated:** [November 20, 2024, 6:53pm UTC](https://community.exalate.com/t/azure-devops-convert-wiki-to-html/5975 "2024-11-20T18:53:20Z")

</div>

This post will show you code snippets you can use to sync over comments from Jira Cloud to Azure DevOps & keep the right format. This will keep the format for Headings, Lists, Url’s, Bold & Italic text and it will also …

---

## [Jira Cloud remove Epic link when removed on remote site](https://community.exalate.com/t/jira-cloud-remove-epic-link-when-removed-on-remote-site/5977)

<div class="topic-metadata">

**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Replies:** 0\
**Last updated:** [November 20, 2024, 7:01pm UTC](https://community.exalate.com/t/jira-cloud-remove-epic-link-when-removed-on-remote-site/5977 "2024-11-20T19:01:13Z")

</div>

First you want to sync over the Epic from one Jira Cloud to another. Outgoing sync Epic.send() Incoming Sync Epic.receive() If you want to make sure epics and their child issues are in sync you can create a trigger …

---

## [Use cases on the old community site](https://community.exalate.com/t/use-cases-on-the-old-community-site/5786)

<div class="topic-metadata">

**Author:** [@francis](https://community.exalate.com/u/francis)\
**Replies:** 0\
**Last updated:** [November 16, 2024, 6:41am UTC](https://community.exalate.com/t/use-cases-on-the-old-community-site/5786 "2024-11-16T06:41:22Z")

</div>

Following use cases are currently available on the old community site. Some of them are already migrated, some are still on the old site. Migrated ADO \<\> Jira Cloud: Date time sync Azure DevOps \<\> Jira Cloud Kee…

---

## [ADO \<\> Jira Cloud: Date time sync](https://community.exalate.com/t/ado-jira-cloud-date-time-sync/5800)

<div class="topic-metadata">

**Author:** [@francis](https://community.exalate.com/u/francis)\
**Replies:** 0\
**Last updated:** [November 17, 2024, 1:50pm UTC](https://community.exalate.com/t/ado-jira-cloud-date-time-sync/5800 "2024-11-17T13:50:13Z")

</div>

If your Jira and ADO are hosted in different time zones, and you need to manipulate the date/time fields so that the same date is kept, here is how we do it. Let us assume: “Due Date” and “Start Date” are custom date/t…

---

## [Controlling GH issue project attributes from Jira](https://community.exalate.com/t/controlling-gh-issue-project-attributes-from-jira/5737)

<div class="topic-metadata">

**Author:** [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Replies:** 0\
**Last updated:** [November 13, 2024, 11:51am UTC](https://community.exalate.com/t/controlling-gh-issue-project-attributes-from-jira/5737 "2024-11-13T11:51:56Z")

</div>

When you Exalate a Jira ticket to GitHub, it would not be assigned to any GitHub project (by default). In this use case, we will control the allocation of the GitHub issue to a project board, but we will base this select…
