Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-68087

As an Admin, I'd like for webhook events to more consistently provide variables in the URL so I can ensure my webhooks work consistently

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 0
    • 4
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

              Unassigned Unassigned
              dnorton@atlassian.com Dave Norton
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: