# Exalate does sometimes not properly reflect moving back tickets into the project with the connection. What can I do?

**URL:** <https://community.exalate.com/t/exalate-does-sometimes-not-properly-reflect-moving-back-tickets-into-the-project-with-the-connection-what-can-i-do/5248>\
**Category:** General Questions\
**Tags:** exalate, migrated\_question\
**Created:** [November 4, 2024, 7:53am UTC](https://community.exalate.com/t/exalate-does-sometimes-not-properly-reflect-moving-back-tickets-into-the-project-with-the-connection-what-can-i-do/5248 "2024-11-04T07:53:20Z")\
**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:53am UTC](https://community.exalate.com/t/exalate-does-sometimes-not-properly-reflect-moving-back-tickets-into-the-project-with-the-connection-what-can-i-do/5248/1 "2024-11-04T07:53:20Z")

</div>

_Originally asked by Johannes Glück on 30 June 2022 [(original question)](https://oldcommunity.exalate.com/questions/58491731)_

* * *

Prerequisites:

We have to Jira instances, both should contain the same tickets (with same IDs) for shared projects. Lets call the Jira instances J1 & J2 the project with a exalate connection EXA and an internal project without the sync INT

Steps:

We have a ticket EXA-1 that is synced between J1 & J2

If now on J1 someone moves EXA-1 to project INT (and it gets INT-1) we stop updating EXA-1 on J2.

Now if someone on J1 moves INT-1 back to EXA it becomes a new ticket EXA-2 (at least with heavily different workflows & statuses)

Problem 1:

BUT it will still be synced to J2 as EXA-1.

Problem 2:

This leads for the next new ticket to be:

EXA-2 on J2 synced with EXA-3 on J1, which makes it really awful to talk about ticket IDs with people seeing only J1 or J2.

What can we do to avoid/mitigate? (moving of tickets is needed to be able to move a bug to a change request etc.)

* * *

---

<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:53am UTC](https://community.exalate.com/t/exalate-does-sometimes-not-properly-reflect-moving-back-tickets-into-the-project-with-the-connection-what-can-i-do/5248/2 "2024-11-04T07:53:21Z")

</div>

_Answer by Ezequiel Consorti on 01 July 2022_

Hi Johannes,

The change of Issue ID is not being produced by Exalate, this is an [expected behaviour](https://community.atlassian.com/t5/Jira-questions/Does-Epic-ID-Story-ID-change-if-you-move-between-Projects/qaq-p/1038769) of Jira. More information on [moving issues](https://confluence.atlassian.com/servicemanagementserver/moving-an-issue-939937218.html) here.

I would highly recommend reaching to the [Atlassian Community](https://community.atlassian.com/) in order to investigate if there is a way to modify the Issue ID.

Additionally, I do not know the specifics of what you are trying to achieve, but an option to avoid these ID modifications could be using Exalate to create a connection between EXA J1 and INT J1 for instance.

Best,  
Ezequiel

* * *