# Mark remote issue as unexalated when unexalating local issue

**URL:** <https://community.exalate.com/t/mark-remote-issue-as-unexalated-when-unexalating-local-issue/4716>\
**Category:** General Questions\
**Tags:** onpremise-jira, exalate, usecase, migrated\_question\
**Created:** [November 4, 2024, 7:18am UTC](https://community.exalate.com/t/mark-remote-issue-as-unexalated-when-unexalating-local-issue/4716 "2024-11-04T07:18:47Z")\
**Posts on this page:** 2\
**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:18am UTC](https://community.exalate.com/t/mark-remote-issue-as-unexalated-when-unexalating-local-issue/4716/1 "2024-11-04T07:18:47Z")

</div>

_Originally asked by Johannes Kern on 20 May 2021 [(original question)](https://oldcommunity.exalate.com/questions/25072561)_

* * *

Hi,

we’re syncing a project in our local Jira Server instance with a project on a remote Jira Server instance and came across the following question:

when I unexalate a local issue in a script is there a way to set a mark on the remote issue that it has been unexalated like changing the status from “Synchronized” to “Unexalated”?

Of course, writing a comment or adding something like UNEXALATED to the title would be a fallback option. I was just wondering whether there is a way which is more obviouse to a remote user.

Thanks in advande

Kind regards

Johannes

* * *

---

<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:18am UTC](https://community.exalate.com/t/mark-remote-issue-as-unexalated-when-unexalating-local-issue/4716/2 "2024-11-04T07:18:48Z")

</div>

_Answer by Francis Martens (Exalate) on 22 May 2021_

An approach is to unexalate from the other side.

Whenever the local issue gets into a state that needs to be unexalated, send this information to the other side by using a customKey

**Local - Outgoing - untested**

```auto
replica.customKeys.doUnexalate = "Yes"

```

On the remote side use the [syncHelper.unexalateAfterProcessing](https://docs.idalko.com/exalate/display/ED/unExalateAfterProcessing) to unExalate the twin

**Incoming sync | Remote | Untested**

```auto
if (replica.customKeys.doUnexalate == "Yes"){

    issue.customFields.isUnexalated.value = "Unexalated on ..." 
    syncHelper.unexalateAfterProcessing()

}

```

Note that the unexalateAfterProcessing is not yet arrived on the Exalate for Jira On Premise (that’s somewhere on the backlog). Check [following snippet](https://stash.idalko.com/snippets/9d5ff1ff461f44c3a92ad463250cb345) for a workaround

* * *