Hi @김혜연 and welcome to the community!
Let me start with a little background on how Webhooks are triggered: When you get into your workflow into the respective transition and open the Post Function section of it, you see all the steps that Jira goes through when this transition occurs.
Namely these are:
As you can see from this list, the first thing that happens is the switch to the target status. The webhook will likely be triggered by the 5th step which is that Jira fires an internal event that things like Apps, Automations and other so called "listeners" can consume.
Taking this into account, it is likely that your JQL is too restrictive and once the webhook would be fired for your ticket, it doesn't have the status "Received" but already "Approved" and hence, the webhook is not executed.
You could fix this in at least two ways:
status CHANGED FROM "Received" to "Approved"
Also "status = Approved" could work. Just play around a little which is where my last tip will be helpful:
How to easily test webhooks
When building webhooks and being unsure whether they are sent and what their payload is, I use a service like https://webhook.site. When you access it, it generates a random hash for you that you can send webhooks/any requests to and it will show you when they came in and what they looked like.
That way you can test whether the webhook was send by Jira.
But please keep in mind not to disclose any sensitive data to this service. You should only be using a test ticket with it and make sure that it is safe to disclose your Jira URL.
I hope that helps!
Greetings
Philipp
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.