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?
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
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.