# How do I make issue numbers the same when syncing two projects using exalate

**URL:** <https://community.exalate.com/t/how-do-i-make-issue-numbers-the-same-when-syncing-two-projects-using-exalate/4772>\
**Category:** General Questions\
**Tags:** exalate, migrated\_question\
**Created:** [November 4, 2024, 7:22am UTC](https://community.exalate.com/t/how-do-i-make-issue-numbers-the-same-when-syncing-two-projects-using-exalate/4772 "2024-11-04T07:22:45Z")\
**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:22am UTC](https://community.exalate.com/t/how-do-i-make-issue-numbers-the-same-when-syncing-two-projects-using-exalate/4772/1 "2024-11-04T07:22:45Z")

</div>

_Originally asked by Michael perry on 12 July 2021 [(original question)](https://oldcommunity.exalate.com/questions/30049397)_

* * *

* * *

#### Comments:

> **Michael perry commented on 12 July 2021**
>
> > I told exalate to sync all issues with another project that I created in a different instance. When I did this issue 1 became issue 14 on the new site and the rest were randomly numbered as well. I cannot seem to make issue 1 be issue 1 on the new project site.

---

<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:22am UTC](https://community.exalate.com/t/how-do-i-make-issue-numbers-the-same-when-syncing-two-projects-using-exalate/4772/2 "2024-11-04T07:22:46Z")

</div>

_Answer by Ariel Aguilar on 12 July 2021_

Hi Michael,  
Keeping the issue key identical over the 2 issue trackers is an advanced configuration, and requires some expert knowledge.  
Check the following document [Is it possible to keep issue key same on both sides?](https://docs.idalko.com/exalate/x/OoIrAQ)

Instead of forcing the issue key to be the same there is an alternative: Work with a global key - which is applicable in all instances.

The idea here is that a custom field ‘Global Key’ is set to the issue key of the initiating issue.  
So whenever an issue is created on Jira A - it gets the key AAA-123. This issue is then exalate towards Jira B, where the key is set to BBB-234 and the global key to AAA-123.

Note that instead of AAA-123 you could also use a hyperlink.

Whenever someone needs to communicate about this issue s/he will mention AAA-123.

Would that work?

Kind regards,

Ariel

* * *