Continuation of a webhook

[Aaron Micallef]

Hey Guys,

I recently managed to do an automation between 2 Jira instances where when we open a ticket in our service based on an issue type condition it will open another ticket in a different Jira instance under a specific project/epic, although it working as we would like it to be, the users want more flexibility on communication between the 2 tickets.

They would like that when a comment is listed in one ticket it will replicate to the other ticket and vice versa.

Cheers Aaron

[Burak Çetin]

Hello, can you explain how you do this synchronization? If you can send it in more detail with pictures.

[Matthias Gaiser _K15t_]

Hi @Aaron Micallef

if you also want to get comments synchronized to the other ticket, you could come up with two other automations like the ones illustrated below.

Please note in order to have them work, you need to save somehow the relation which issue on the source side is linked to which issue on the destination side. The easiest way I can see is to define a custom field in the destination Jira where you store the issue key of the source side.

Source Jira

• When: Issue Commented
• Then: Send web request (to the other Jira)
  • Make sure to send the issue key along with the comment.

Destination Jira

• When: Incoming Webhook
  • Run a JQL search which uses the received issue key and matches it with your custom field where you store the source issue keys, e.g. remoteKey = {{webhookData.issueKey}}
• Then: Comment on issue

Does this help?

Cheers,
Matthias.

PS: If that sounds too complicated to you, you can also get an issue sync app from the marketplace. They're specialized in these scenarios and you don't need to get that technical. I'm part of the team behind Backbone Issue Sync and happy to help further.

[Aaron Micallef]

Hello @Matthias Gaiser _K15t_ 

Thank for this will check this out, also perhaps rather than being able to comment could we perhaps be able to link the 2 issues together while the automation is being performed.

That would be enough as we would see the status off each issue from both instances.

Cheers Aaron 

[Matthias Gaiser _K15t_]

If you have an application link between the instances, of course you could also create a remote issue link between both issues.

I think, Atlassian still doesn't support this directly in Automation, but you can use Jira's REST API to create remote links. These linked docs are for Server, but they're also valid for Jira Cloud. We have an automation running which links issues between Jira instances.