Hey guys, I have a question regarding jira event webhooks, specifically about jira changelog items. I recently encountered a webhook event where a single webhook event sent more than one changelog items.
During my initial development, I never encountered this. I always thought single change will trigger single webhook event. Turns out after doing some research, there are ways to achieve it and one of them is by using Automation rule where it could trigger multiple field changes.
My question is: How do I trigger multiple changelog items with specific changes include “Status change from A to B” and “Issue getting unlinked from its epic”?
I tried playing around with jira automation, but it seems I always get two different webhook events still instead of one webhook events with two changelog items for scenario I asked above since the automation differentiate between transition (status update) and workitem update (epic unlinked)
Hello @KevinAndrio
I’m not aware of any mechanism in Jira’s Automation that allows two or more changes to be performed simultaneously and thereby ‘combined’ into a single event in the changelog, and then a single webhook event firing that contained two changelog items in the payload. Do you have a full copy of that original webhook event and that payload?
Can you advise about the source of the ‘research’ you did that describes “there are ways to achieve it” in Jira Automation?
Hi @sunnyape
Unfortunately I do not have a copy of that original webhook. I detected this through the failed handling on my app’s side that is expecting just 1 changelog item. But I don’t have the original webhook payload of the actual event.
On the ways to achieve it, this is the forum thread where I found it’s possible: Solved: How to update multiple fields on linked issues usi...
And also, I tried jira automation rule on my own where I setup a rule that updates a few fields based on a certain change: Create and edit Jira automation rules | Cloud automation Cloud | Atlassian Support
1 Like
Well I’ll be!! That does cause a single issueUpdated event to be fired and all the changes to those fields to be sent in a single webhook payload, despite being logged as separate changes in the change log. I’ve never encountered that.
As to how to get the specific automation combination you’re after to achieve the same outcome, I don’t think it’s possible, as the automation actions for transitioning an Issue and deleting all the links are completely separate. Even if you were to use a web request action and send requests to Jira’s REST API, you would need two separate requests, and therefore generate two separate webhook events.
Since your question is essentially about how to do something with Jira’s built-in Automation functionality, you’re best to try over on the public Jira Community forum to see if anyone has any ideas.
Good luck!