# How do we create a remote issue with specific issue key based on the custom field on a initiating issue?
**URL:** https://community.exalate.com/t/how-do-we-create-a-remote-issue-with-specific-issue-key-based-on-the-custom-field-on-a-initiating-issue/4059
**Category:** General Questions
**Tags:** onpremise-jira, migrated\_question
**Created:** [November 4, 2024, 6:25am UTC](https://community.exalate.com/t/how-do-we-create-a-remote-issue-with-specific-issue-key-based-on-the-custom-field-on-a-initiating-issue/4059 "2024-11-04T06:25:44Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@xl8bot](https://community.exalate.com/u/xl8bot)
#### Post date: [November 4, 2024, 6:25am UTC](https://community.exalate.com/t/how-do-we-create-a-remote-issue-with-specific-issue-key-based-on-the-custom-field-on-a-initiating-issue/4059/1 "2024-11-04T06:25:44Z")
_Originally asked by Samip K Banker on 30 August 2019 [(original question)](https://oldcommunity.exalate.com/questions/2592772)_
* * *
We want create a remote issue with specific issue key based on the custom field on a initiating issue?
Project A (Initiating project)
```
cusotmfield value : ABC\-123
```
Project B (Remote Project)
```
project Key \= ABC
```
when we sync issue between Project A and B… we wnat to create ABC-123 in Project B… and not use the issue key for the issue in Project A?
* * *
#### Comments:
> **Francis Martens (Exalate) commented on 30 August 2019**
>
> > If I understand the request correctly.
>
> - On A you have a customField - ‘Remote Key’
> - Exalate is triggered on A1 - creating issue B1 (on B) with issue key ABC-123
> - What is the method to have ‘Remote Key’ on A1 set to ‘ABC-123’
>
> ?
> **Samip K Banker commented on 30 August 2019**
>
> > Francis:
> > We want to do 3 way sync…
>
> **Project A :**
>
> ```
> ABC\-123 is created and will be synced to Project B
>
> ```
>
> **Project B :**
> B1 : where Remote Key = ABC-123
> Once B1 is Approved for 3rd level sync then that issue will be synced to Project C
>
> **Project C : (project key will be ABC)**
> We want issue ABC-123 created that will be in sync with B1...
> Assumptions here is that ABC-123 will not be there in Project C.
>
> Hope this helps to understand our need.
> ~Samip
---
### Author:  [@xl8bot](https://community.exalate.com/u/xl8bot)
#### Post date: [November 4, 2024, 6:25am UTC](https://community.exalate.com/t/how-do-we-create-a-remote-issue-with-specific-issue-key-based-on-the-custom-field-on-a-initiating-issue/4059/2 "2024-11-04T06:25:45Z")
_Answer by Francis Martens (Exalate) on 02 September 2019_
Keeping the issue key identical over the 3 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. Whenever that issue is exalated a second time to Jira C, the issue in C gets CCC-345 and global key 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?
* * *