-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
0
-
4
-
Summary
Not all webhook events provide the same URL variables. This can lead to scenarios where a single webhook has multiple events - but the webhook will not always execute consistently, because some variables will not be present.
Currently, the list of variables is:
- board related webhooks: board.id
- sprint related webhooks: sprint.id
- attachment related webhooks: attachment.id
- comment related webhooks: comment.id
- issue related webhooks: issue.id, issue.key, project.id, project.key
- project related webhooks: project.id, project.key
- version related webhooks: project.id, project.key, version.id
- version merge webhook: mergedVersion.id
- worklog related webhooks: worklog.id
The following event types do not provide any URL variables:
- Issue Link related webhooks:
- Features status change related webhooks (voting, watching, etc)
(Please note that this list may change in the future)
Suggested Solution
All webhook events should provide a bare minimum of variables, where it makes sense to do so.
Why this is important
This is important so webhooks operate consistently when multiple events have been selected.
- Discovered while testing
-
JRASERVER-67894 Webhook Variables do not work for webhook event Link created
-
- Closed
-
- is related to
-
JRASERVER-68086 As an Admin, the webhooks UI does not clearly show which variables I can use within a URL
- Gathering Interest