Thank you for voting and commenting on this request. After taking into account actual usage of different webhook events and potential workarounds for restricting them, we decided to action in the following ways:
- We are splitting this collective request into separate issues - each for individual webhook event - in order to make it more clear what is the status of JQL support for each of webhook events respectively, and to give you opportunity to express demand for specific improvements. From now on you can refer to the following issues for JQL filtering of:
- Comment webhooks -
- Attachment webhooks - JRACLOUD-68594
- Worklog webhooks - JRACLOUD-68595
- Since December 2017, JQL filtering is available for Comment webhooks. For the remaining webhook events, it is still possible to restrict them by substituting variables in the webhook URL.
- We have updated Jira Cloud Webhooks documentation to make it more clear that JQL filtering is only supported for a subset of webhook events, and what those events are.
- As of January 2018 JQL filtering of Attachment, Worklog and Issue Link webhooks (as well as others not mentioned as JQL enabled in the documentation) is not supported, and that works by design. Therefore, adding such functionality is treaded as improvement suggestion in the newly created issues.
- At this moment we do not have plans to add JQL filtering for the remaining webhook events, but we can revisit that decision in the future.
- As a consequence of splitting the issue, and because the main use case was addressed, we’re closing as Fixed.
We understand that your expectations expressed in this issue have not been fully addressed, but after balancing the value of competing priorities we’ve determined that focusing on Comment webhooks would provide the biggest value for Jira Cloud app developers. To that end, I hope you appreciate the transparency of this update.
Product Manager, Jira Cloud Platform