nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Branching on JQL failes for Incoming Webhook Trigger rule

Jimmy Petersson

Hi,

Context: using Jira Data Centre

My use-case involves triggering a project automation rule using an incoming webhook from another project automation rule on the same Jira server. The send- and receive webhook works great and can exchange data.

Incoming Webhook Rule

However, the branching on JQL is never executed for my receiving rule as is evident from the below audit log as Debug 3 tag is not shown in audit log. The rule skips branching and goes :

Initially I suspected the received data used to craft the JQL was incorrect, so I hardcoded the JQL statement to one specific issue that exist on the server (as can be seen below).

But this did not resolve the issue.

If I modify the trigger to a scheduled one, and run the rule manually, the branching condition works as expected, and Debug 3 tag appears in audit log:

Are there any known issues/limitations when it comes to branching logic when using Incoming Webhook trigger?

If not, any suggestions for further troubleshooting would be much appreciated.

Best Regards

//Jimmy

Accepted answers

Bill Sheboy

Hi @Jimmy Petersson

First thing, I am using Jira Cloud so I cannot confirm the following for Server/Data Center version...

There is an defect that when the incoming webhook trigger fires, JQL in the rule is executed as an anonymous user: https://codebarrel.atlassian.net/browse/AUT-547

That one looks like it was fixed, but I wonder if you change the user the rule runs under if that will impact the results.

Regardless, I recommend submitting this one as a ticket to Atlassian Support to review: https://support.atlassian.com/contact/#/

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Jimmy Petersson

First thing, I am using Jira Cloud so I cannot confirm the following for Server/Data Center version...

There is an defect that when the incoming webhook trigger fires, JQL in the rule is executed as an anonymous user: https://codebarrel.atlassian.net/browse/AUT-547

That one looks like it was fixed, but I wonder if you change the user the rule runs under if that will impact the results.

Regardless, I recommend submitting this one as a ticket to Atlassian Support to review: https://support.atlassian.com/contact/#/

Kind regards,
Bill

Jimmy Petersson

Hi Bill,

Thanks for sharing.

There is something fishy with my combo of incoming webhook trigger and branch statement. Will do some more digging around before submitting a defect ticket.

B R

//Jimmy

Grant Kadokura_1mo7jq

@Jimmy Petersson I'm having the same issue, webhook not triggering JQL branch. I similarly tried hardcoding and still nothing. Did you figure out what was going on?

Grant Kadokura_1mo7jq

@Jimmy Petersson I figured out what was causing my issue, I had failed to set this webhook field properly

2023-11-29 08_17_51-Clipboard.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

webhook

jira-data-center

automation