Jira Cloud webhook error 'No issues from the webhook'

[Yi Meng]

I'm trying to use webhook to create a new issue in Jira instance B when issues changed in Jira instance A. Both Jira instances are cloud.

I create a automation rule in Jira instance B with incoming webhook to create a new issue.

In Jira instance A, I create a webhook as Jira admin. The events are issue create and update. 

When I make changes in Jira instance A, no issue is created in Jira instance B. 

I check the audit log, it shows that 'No issues from the webhook'. 

From the audit log, it looks like the webhook was successfully triggered. However, the webhook may not contain required data.

I can't find a way to check what Jira instance A has sent out in the webhook. Can anyone help me on this? Thanks.

[Kai Becker · Accepted solution]

Hi @Yi Meng 

could you post the config of your incoming webhook? 

This type of automation rule might be a little confusing first. To make things a little bit clearer:

• a Jira webhook sends a complete JSON structure of the issue, containing all data
• an incoming webhook trigger in Automation requires one or more issue keys provided, to make changes to these issues
• the solution you are trying to achieve requires a little bit more configuration
  • create a rule with incoming webhook (you should have this by now)
  • set the incoming webhook to "No issues from the webhook" (this prevents the rule from trying to detect an issue - this is your current error)
  • add an action to create an issue
  • Map the JSON data of the fields of the issue you want to create
    • e.g. in Summary field, set to {{webhookData.issue.summary}}
      An example of a webhook JSON can be found here
      
  • For debugging purposes, you can also add an log action to your rule and log out certain parts of the webhook data, e.g. {{webhookData.issue}}

Hope this helps to get you started.

[Yi Meng]

Thanks @Kai Becker 

I've set incoming webhook to 'No issues from the webhook'. This solved my orignial issue. Thank you so much. 

But I still got error about creating issue. 

In the log, I can see all the payload from the webhook. Any suggestions? Thanks.

[Kai Becker]

Hi @Yi Meng 

I guess the smart value for description is wrong. Looks like you forgot the issue in between.

What is the current error? For testing you could replace the smart values with plain text to check that the error is not permission related.

[Yi Meng]

You're right. I changed {{webhookData.issue.summary}} to a plain text and I can successfully create a new issue. So, it's most likely webhookdata  smart value related issue. 

I've changed the smart value to {{webhookData.issue.fields.summary}} for summary field, and {{webhookData.issue.fields.description}} for description. 

And now it works fine. Thank you so much. 

[Yi Meng]

@Kai Becker 

You mentioned I should

• set the incoming webhook to "No issues from the webhook" (this prevents the rule from trying to detect an issue - this is your current error)

Can you tell me more about it? When I should choose the other 2 options? I don't find a related document yet. Thank you. 

[Kalyan Sattaluri]

Hello @Yi Meng 

2 things.

In Instance A, in your "Send web request" action, make sure you selected to include "Issue Data" in web request body. (see screenshot)

In Instance B, after your trigger, Do action -> Log action and log -> {{webhookData}} to capture what was sent.

Please share screenshots of your Instance B rules audit log after.

[Ari Raatikainen]

As per my experiments {{webhookData}} itself doesn't return anything but root (empty). But if the JSON body received sent was

{

    "key": "ITS-4818",

    "event" : "resolve"

}

then 
{{webhookData.key}} returns "ITS-4818"
{{webhookData.event}} returns "resolve"