Note
We've packed up and moved from Confluence to Discourse to bring you a better, more interactive space. Out of courtesy we didn't migrate your user account so - you will have to signup again
The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
Hi,
I need each issue on my local instance (Jira Cloud) to be linked to an already existing issue on the remote side (Jira Data Center) with the same issue key. I am using a Visual Mode connection and need this to be done via a script under the connection rules as I need every issue that is exalated to follow this process. I have pre-created all necessary issues on the remote side and this is necessary due to our code (Fisheye) being managed in Jira via issue key.
I found the helpful code below from feedback on this page provided by Francis Martens (Exalate) .
It is mentioned that the code should be added to the incoming sync and that the process for fetching the target issue id depends on the environment.
Since the scripts for the Visual Mode connection are applied on both sides, what adjustments need to be made to this code for it to create the same result from a visual mode script? How would I also fetch the issue ID in this particular environment (Jira to Jira)? Any help would be much appreciated!
Hi Francis Martens (Exalate) , thanks for the quick response. I am not sure I understand the applicability to the visual mode where both sides are handled in the same script.
I am looking for code in the same format as the examples provided for visual mode scripts with your_instance_shortname format. I am not very familiar with groovy scripts but want to use your product in this way. Can you provide the example code in this format so that myself and others who need to use visual mode and match issue keys in this way can have the code to do so? Thanks!
You can insert the code provided in the snippet and adapt the shortnames to your case.