# How to not trigger sync when issue link is created

**URL:** <https://community.exalate.com/t/how-to-not-trigger-sync-when-issue-link-is-created/4382>\
**Category:** General Questions\
**Tags:** onpremise-jira, migrated\_question\
**Created:** [November 4, 2024, 6:52am UTC](https://community.exalate.com/t/how-to-not-trigger-sync-when-issue-link-is-created/4382 "2024-11-04T06:52:52Z")\
**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, 6:52am UTC](https://community.exalate.com/t/how-to-not-trigger-sync-when-issue-link-is-created/4382/1 "2024-11-04T06:52:52Z")

</div>

_Originally asked by Berry Kersten on 06 October 2020 [(original question)](https://oldcommunity.exalate.com/questions/20119841)_

* * *

Hi,

When an issue is under sync AND an issue link is created (e.g. relates to), then it triggers a sync (as the issue is updated). This is unwanted as there’s nothing new to sync in this use case.

How can I disable this ‘trigger’, so that the issue is not synced when an issue link is created?

* * *

---

<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, 6:52am UTC](https://community.exalate.com/t/how-to-not-trigger-sync-when-issue-link-is-created/4382/2 "2024-11-04T06:52:53Z")

</div>

_Answer by Francis Martens (Exalate) on 06 October 2020_

Normally it shouldn’t trigger a message if nothing changed.  
Can you try following approach

- Create a local connection
- Add in the incoming sync a ‘throw new Exception(“Hello”)’
- Start a sync  
This will throw an error
- Collect the remote replica from the error details (call it replica1)
- Comment out the exception
- Resolve and retry the error
- Uncomment the exception
- Add an issue link
- Collect the remote replica again from the error details (call it replica2
- Compare replica1 and replica2

Let us know

* * *
