Skip to content

Ensure issuable state changes only fire webhooks once

What does this MR do?

Ensure issuable state changes only fire webhooks once

Are there points in the code the reviewer needs to double check?

Check to see if the tests could be refactored, possibly into a shared context as they are very similar?

Why was this MR needed?

Webhooks were fired twice when issuables were reopened or closed. Once for the status change and once for the update operation

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Closes #25339 (closed)

Merge request reports

Loading