-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
1
-
Severity 2 - Major
-
Summary
The webhooks are currently not correctly honoring the conditions with attachments. If the user creates two webhooks (with each webhook targeting its own specific project) and both webhooks have the attachment conditions checked, attaching an attachment to any issuetype will trigger both webhooks regardless of the project that the issue was created in.
Steps to Reproduce
- Create two webhooks targeting different projects in the JQL query conditions
- For example: 1 webhook should have JQL query: project = ABC, the other webhook will have: project = DEF
- Both webhooks should have conditions selected:
- Attachments:"created" and "deleted" selected.
- Issue: "created" and "updated" selected.
- Comment: "created" and "updated" selected
- Both webhooks should be enabled
- Go to one of your projects specific in your webhooks and create an issue. Attach an attachment
- Notice that once an attachment is attached, both webhooks will trigger even when the attachment is not on that specific project
Expected Result
When attaching an attachment, the webhook in which the issue/attachment resides should only be the one triggering. All other webhooks should not trigger according to its conditions.
- duplicates
-
JRACLOUD-68594 Enable JQL filter for "Attachment" webhook events
- Closed