# Jira Cloud to Jira Cloud: How to sync request types?

**URL:** <https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718>\
**Category:** General Questions\
**Tags:** exalate, cloud-jira, jira-cloud, request-type, requesttypes\
**Created:** [February 9, 2026, 7:14pm UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718 "2026-02-09T19:14:11Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stian](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@Stian](https://community.exalate.com/u/Stian)\
**Post date:** [February 9, 2026, 7:14pm UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/1 "2026-02-09T19:14:11Z")

</div>

Hi,

We are trying to sync request types from one Jira Cloud instance to another, but we can’t seem to set it on the receiving side.

We can see in the Entity Sync that the request type is being sent, but it is not updated on the local entity:

**Remote:**  
“customFields”: {  
“Request type”: {  
“id”: 10010,  
“name”: “Request Type”,  
“uid”: “10010”,  
“type”: “VP\_ORIGIN”,  
“value”: {  
“requestTypeId”: “28”,  
“requestTypeName”: “General Incident”,  
“serviceDeskId”: “2”,  
“serviceDeskProjectName”: “Site B”,  
“serviceDeskProjectKey”: “SITEB”  
}  
}  
},

**Local:**  
“customFields”: {  
“Request Type”: {  
“id”: 10010,  
“name”: “Request Type”,  
“uid”: “10010”,  
“type”: “VP\_ORIGIN”,  
“value”: {  
“requestTypeId”: “232”,  
“requestTypeName”: “General Incident”,  
“serviceDeskId”: “36”,  
“serviceDeskProjectName”: “Site A”,  
“serviceDeskProjectKey”: “SITEA”  
}  
}  
},

We have the same name of the request type on both the remote site and the local site, but if we change it the sync is does not update the request type field.

**We have tried following the following guide:**

> **[Sync Customer Request Type in Jira Service Desk – Ex](https://docs.exalate.com/docs/jsd-customer-request-type-sync)**
>
> Learn how to sync the customer request type field in Jira Service Desk using Exalate Docs. Understand how to configure and manage field synchronization effectively.

Any idea of what we can do to fix this?

---

<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:** [February 9, 2026, 7:14pm UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/2 "2026-02-09T19:14:30Z")

</div>

Syncing the “Request Type” field between two Jira Cloud Service Management instances can be tricky because the request type is tightly linked to both the issue type and the service desk project. Here’s what you need to know and do:

1. **Outgoing Sync (Source Side):**  
Make sure your outgoing sync script includes:

2. **Incoming Sync (Destination Side):**  
On the receiving side, you need to explicitly set the request type in your incoming sync script. Use:

3. **Important Notes:**

4. **If It’s Still Not Working:**

For more details, check out the official documentation:

- [How to Sync Customer Request Type Field in Jira Service Desk on Jira Cloud](https://docs.exalate.com/docs/jira-cloud-how-to-sync-customer-request-type-field-in-jira-service-desk)
- [How to Sync Request Type using Visual Mode in Jira Service Management](https://docs.exalate.com/docs/how-to-sync-request-type-using-visual-mode-in-jira-service-management)

If you follow these steps and ensure the request type, issue type, and project are all aligned, the sync should work as expected!

---

<div class="post-metadata">

**Author:** ![mathieu](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/mathieu/32/370_2.png) [@mathieu](https://community.exalate.com/u/mathieu)\
**Post date:** [February 18, 2026, 3:32pm UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/3 "2026-02-18T15:32:53Z")

</div>

Can you share your current code please?

This needs to be outside of the if(firstSync) codeblock to work.

Kind regards,

Mathieu Lepoutre

---

<div class="post-metadata">

**Author:** ![Stian](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@Stian](https://community.exalate.com/u/Stian)\
**Post date:** [February 20, 2026, 8:21am UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/4 "2026-02-20T08:21:32Z")

</div>

![image](https://europe1.discourse-cdn.com/flex018/uploads/exalate1/original/1X/9e23aa847d1239bd21ea36569c9840dc793ce43a.jpeg)

Hi Mathieu,

Thanks for looking into this.

Please see the attached image for the code on both sides.

Best regards

Stian

---

<div class="post-metadata">

**Author:** ![mathieu](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/mathieu/32/370_2.png) [@mathieu](https://community.exalate.com/u/mathieu)\
**Post date:** [February 20, 2026, 10:18am UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/5 "2026-02-20T10:18:23Z")

</div>

> [@Stian](#):
>
> Hi,
> 
> We are trying to sync request types from one Jira Cloud instance to another, but we can’t seem to set it on the receiving side.
> 
> We can see in the Entity Sync that the request type is being sent, but it is not updated on the local entity:
> 
> **Remote:**  
> “customFields”: {  
> “Request type”: {  
> “id”: 10010,  
> “name”: “Request Type”,  
> “uid”: “10010”,  
> “type”: “VP\_ORIGIN”,  
> “value”: {  
> “requestTypeId”: “28”,  
> “requestTypeName”: “General Incident”,  
> “serviceDeskId”: “2”,  
> “serviceDeskProjectName”: “Site B”,  
> “serviceDeskProjectKey”: “SITEB”  
> }  
> }  
> },
> 
> **Local:**  
> “customFields”: {  
> “Request Type”: {  
> “id”: 10010,  
> “name”: “Request Type”,  
> “uid”: “10010”,  
> “type”: “VP\_ORIGIN”,  
> “value”: {  
> “requestTypeId”: “232”,  
> “requestTypeName”: “General Incident”,  
> “serviceDeskId”: “36”,  
> “serviceDeskProjectName”: “Site A”,  
> “serviceDeskProjectKey”: “SITEA”  
> }  
> }  
> },
> 
> We have the same name of the request type on both the remote site and the local site, but if we change it the sync is does not update the request type field.
> 
> **We have tried following the following guide:**
> 
> [Sync Customer Request Type in Jira Service Desk | Exal](https://docs.exalate.com/docs/jsd-customer-request-type-sync)
> 
> Any idea of what we can do to fix this?

Dear Stian

I had a deep dive into this.

The Request Type field in Jira Service Management cannot be updated on existing issues. This is a limitation of the Jira Cloud platform itself, not just Exalate. The Request Type can only be set when an issue is first created through the Service Desk API. Jira Cloud does not expose an API to change it afterward.

A workaround is to use the httpClient (but there is no endpoint from atlassian out) or a text field where you store the Request Type.

Kind regards,

Mathieu Lepoutre

---

<div class="post-metadata">

**Author:** ![Stian](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@Stian](https://community.exalate.com/u/Stian)\
**Post date:** [February 20, 2026, 12:09pm UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/6 "2026-02-20T12:09:46Z")

</div>

Thanks for the clarification, Mathieu.

We do have the need to change the request type from time to time, so we will look into a workaround for this. Perhaps by syncing a custom field called “Remote Request Type” and an automation rule to perform the actual changing of the request type based on that.

Best regards

Stian

---

<div class="post-metadata">

**Author:** ![Dhiren](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/dhiren/32/356_2.png) [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Post date:** [February 23, 2026, 6:08am UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/7 "2026-02-23T06:08:36Z")

</div>

Hi Stian,

Although I am not 100% sure what I am suggesting here would work 100% but it’s still worth a shot.

What Mathieu (my colleague) suggested above is what I think as well, and changing the Request Type after the issue creation is a limitation and the only way out here would be httpClient().

Here’s an example for you which you can try.

```auto
if(firstSync){
    issue.projectKey = "DEMO"
   // Set type name from source issue, if not found set a default
   issue.typeName = nodeHelper.getIssueType(replica.type?.name, issue.projectKey)?.name ?: "Task"
   issue.summary = replica.summary
   store(issue) 
}

// We do a store(issue) so the issue.key will be created on the first sync and the request type will be set
// Note that customfield_10010 is the request type field and 33 is the request type id

def url = "/rest/api/3/issue/${issue.key}/"
def data = "{\"fields\": {\"customfield_10010\": \"33\"}}"
httpClient.put(url, data)

```

Let me know how it goes!

Thanks, Dhiren

---

<div class="post-metadata">

**Author:** ![Stian](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@Stian](https://community.exalate.com/u/Stian)\
**Post date:** [February 24, 2026, 9:06am UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/8 "2026-02-24T09:06:34Z")

</div>

Hi Dhiren,

Thanks for providing the API call.

We have tested this with a mapping of “remote request type name” to “local request type id”, and this works to both store the request type upon creating the ticket and when updating the request type .

Best regards

Stian

---

<div class="post-metadata">

**Author:** ![Dhiren](https://dub1.discourse-cdn.com/flex018/user_avatar/community.exalate.com/dhiren/32/356_2.png) [@Dhiren](https://community.exalate.com/u/Dhiren)\
**Post date:** [February 25, 2026, 9:31am UTC](https://community.exalate.com/t/jira-cloud-to-jira-cloud-how-to-sync-request-types/7718/9 "2026-02-25T09:31:05Z")

</div>

Hi @Stian ,

Great to hear, it works for you.

Thanks, Dhiren