# Skip certain statuses

**URL:** <https://community.exalate.com/t/skip-certain-statuses/5220>\
**Category:** General Questions\
**Tags:** exalate, migrated\_question\
**Created:** [November 4, 2024, 7:51am UTC](https://community.exalate.com/t/skip-certain-statuses/5220 "2024-11-04T07:51:17Z")\
**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, 7:51am UTC](https://community.exalate.com/t/skip-certain-statuses/5220/1 "2024-11-04T07:51:17Z")

</div>

_Originally asked by Samuel Carter on 20 May 2022 [(original question)](https://oldcommunity.exalate.com/questions/42838852)_

* * *

Is it possible to not trigger a sync when a certain status is set? We have a few statuses where wouldn’t want the connected ticket to try and transition.

Between our two instances of JIRA, we do not have 1:1 statuses, so we find ourselves getting sync errors because it cannot find an corresponding status.

The only way I’ve been able to tackle this is by adding more statuses between the workflows, so Exalate doesn’t throw an error.

Our use case is JIRA is internal, and JSM is external for customers to view. Our JIRA workflow is much more granular than the JSM one, customers only need a few of these equivalent statuses.

* * *

---

<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, 7:51am UTC](https://community.exalate.com/t/skip-certain-statuses/5220/2 "2024-11-04T07:51:18Z")

</div>

_Answer by Samuel Carter on 31 May 2022_

Hi M. Ashar Iqbal,

I have configured as per your link, specifically from the part of the page:

## Configuration

Let’s consider you already have the Connection configured between two JIRA Instances.

Now you need to **configure status**  **synchronization**

### Map statuses

EXALATE FROM 4.7.3

**Outgoing sync**

To send the status use the code below

| 1 | `replica.status = issue.status` |
| --- | --- |

**Destination side**

**Incoming sync**

| 123 | `def` `statusMap = [``"Done"``:``"Resolved"``,``"In Progress"``:``"In Action"``]``// ["remote status name": "local status name"]``def` `remoteStatusName = [replica.status.name](http://replica.status.name)``issue.setStatus(statusMap[remoteStatusName] ?: remoteStatusName)` |
| --- | --- |

if status are the same on both sides you can just do:

| 1 | `issue.status = replica.status` |
| --- | --- |

This is exactly how I have mine set up.

I would like to be able to have certain statuses not trigger a sync, there are a number of statuses I don’t have corresponding statuses for between the two JIRA instances.

Thanks and regards,

Sam

* * *

---

<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, 7:51am UTC](https://community.exalate.com/t/skip-certain-statuses/5220/3 "2024-11-04T07:51:19Z")

</div>

_Answer by M. Ashar Iqbal on 20 May 2022_

Hi Samuel Carter ,

Have you tried configuring the ‘Statuses’ by following this guide “[Status synchronization on Jira Server](https://docs.idalko.com/exalate/x/14YrAQ)”?

Please let me know if it does not work, and we’ll look for any other solution (if any available).

Thank you,

Ashar

* * *