[bug]: event updates trigger multiple webhook calls

[sonoerinLSN]

Is there an existing issue for this?

• [x] I have searched the existing issues

Current behavior

When I update the state of a issue in any of my projects, multiple (usually 3) events trigger Webhook calls. this makes handling the webhooks difficult (and expensive if using something like n8n).

What should happen is when the work item state changes that should be a singular event. Also, it would be nice if a webhook could be for a single project, not all encompassing. Although have one main Webhook for all events is nice to have.

I am attaching a screenshot of one of my webhooks for referebce

Steps to reproduce

1. Have an endpoint prepared to handle the Webhook
2. Configure the Webhook to fire on Work Items individual event
3. Change the state of a work item issue from one to another - such as "Backlog" to "In Progress"
4. monitor the Webhook to see the events being fired off

Environment

Production

Browser

Google Chrome

Variant

Cloud

Version

latest

[dwichers]

I am also experiencing this issue. Every time I receive two webhook calls, I have managed to filter them based on the values in:

"activity": { "field": "value" }

By ignoring one of them, I am able to proceed with my work. However, it would be great to have a proper fix for this.

Update: this only works for issue type updates. If I change the name of an issue two activity field with 'name' value will be sent. That is quite a bummer, I think I'll have to implement a lock system that disables incoming webhooks until the first one is done :/