You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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/#/