-
Type:
Suggestion
-
Resolution: Unresolved
-
None
-
Component/s: Webhooks
-
None
In very big Jira implementations, enabling Webhooks on "Update tickets" events could kill Jira's performance, because the JQLs engine starts to be flooded with tons of queries.
As a user, I would like to narrow the webhook scope before executing any JQL with some fixed parameters, like issue type list, project lists, the priorities...