Webhook - mirror 2 instances

[Amali]

Hey Community,

I have the following requirement.
There are 2 projects in 2 different instances. If an issue is created in 1 project in instance A or an update happens, both instances A & B need to register it. For example, if an issue is created in 1 project in instance A, instance B should create the same issue. If there is an update in issue in instance B, the same issue in instance A should reflect that update (bidirectional). How to set this up in Jira using automation webhook? If there a way to mirror all changes in any instance in the other?

[Joseph Chung Yin]

@Amali -

Need clarification on your definition of two different instances - Are you stating that project A is in one site and project B is in another completely different site?  In another word, you have to separate Jira server envs.

If above is valid (my understanding), then the only way for you to use automation rule is incorporating the action of "Send web request" to push webhook json body to your target site, and then create custom process (outside of automation rule) to parse through the json body content and conduct the needed issue updates.  The custom process is done using REST APIs.

A standard automation rule will not be able to conduct your process between two different sites based on my knowledge/experiences.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Amali]

Hi @Joseph Chung Yin

Thanks for the response.

You are correct. The projects are hosted on 2 different servers.

Right now, I tried to 'send web request' and was trying to use 'incoming webhook' to retrieve the data. 

But the incoming webhook fails with different errors every time. 

I'm new to webhook and I'm not able to figure out how to achieve this request yet.

[Joseph Chung Yin]

@Amali -

Take a look at following reference page on working with incoming webhook - https://confluence.atlassian.com/jirakb/working-with-incoming-webhook-data-in-automation-for-jira-1125878776.html

It is a bit difficult to advise as you mentioned that it fails with different errors every time in your automation rule using "incoming webhook" trigger.

Hope this helps.

Best, Joseph

[Matthias Gaiser _K15t_]

Hey @Amali

I'd like to empasize what @Joseph Chung Yin already said. If you want to realize your use case with Automations, you would have a set of various automation rules.

If you really want to go that way, you need to get yourself familiar with Automation in general, smart values and JSON. If you feel familiar, you need to look into the error messages you get, e.g.:

• You must specify a summary of the issue
  In the create issue action, you should check again what you specify for the summary, obviously Jira does not recognize it.
• Issue does not exist or you do not have permission to see it
  It seems that the automation can't view the issue. Should it exist? What do you expect?

To be honest, I'd rather recommend that you look into an issue synchronization app from the Atlassian Marketplace, then you don't need to handle all the updates in this technical manner. You can call me also biased, because I'm part of the team of Backbone Issue Sync which is such an issue sync app - but it's still my honest advice after trying out to sync issues across instances with Jira Automation.

All the best for your project,
Matthias.