Events and event families

Events and event families

The Events tab on the webhook form decides when the webhook fires. Four families, four tabs. Each tick subscribes the webhook to one specific Jira event.


The four families

Each family corresponds to one tab on the Events section of the form. The number badge on the tab shows how many events you have ticked in that family.

Issue Related Events

What it covers: anything that happens to an issue.

  • Lifecycle — Issue created, Issue updated, Issue deleted.

  • People — Issue assigned, Issue mentioned (in description / comment).

  • Comments — Comment created, updated, deleted.

  • Worklogs — Worklog created, updated, deleted.

  • Attachments — Attachment created, deleted.

  • Issue links — Issue link created, deleted.

This tab is the only one with a JQL filter field at the top — see JQL filtering.

Project Related Events

Project lifecycle and child entities (versions, components):

  • Project created, updated, deleted, archived, restored.

  • Version created, updated, released, unreleased, deleted, moved.

  • Component created, updated, deleted.

No JQL filter on this tab — JQL is an issue concept.

User Related Events

  • User created.

  • User updated.

  • User deleted.

Most useful for SCIM-adjacent integrations and audit pipelines.

Configuration Events

Schema and admin changes — the things a Jira admin does, not what a project member does:

  • Filter created, updated, deleted.

  • Issue type created, updated, deleted.

  • Custom field created, updated, deleted.

  • Field context created, updated, deleted.

  • Workflow created, updated, deleted.

Useful for compliance trails ("who added a custom field?") and for keeping an external schema mirror in sync.


How to pick events

Tri-state parent checkboxes

Each family has parent groupings (e.g., Comments groups Created / Updated / Deleted). The parent checkbox is tri-state:

  • ☐ — none ticked.

  • ☑ — all children ticked.

  • ⊟ — some ticked.

Click the parent to bulk-toggle: all-on or all-off depending on current state.

At least one event is required

The form refuses to save with zero ticked across all four tabs.

Across families

You can mix freely. One webhook can subscribe to Issue created (Issue tab) and User created (User tab) and Custom field created (Configuration tab). The receiver will see different payload shapes depending on which event fired — use the event field at the root of the payload to dispatch on the receiving side.


Picking the right granularity

The most common mistake: ticking too much, then trying to filter on the receiver. Filter at source instead.

Goal

Tick

Goal

Tick

"I want to know when an issue was just created"

Issue created

"I want a notification only when status changes"

Issue updated + filter on the receiver by changelog.items containing status — Webhooks Pro doesn't have a status-only event

"Track every comment, including edits and deletes"

Comment created, updated, deleted

"Audit trail of admin changes"

Filter created/updated/deleted, Custom field created/updated/deleted, Workflow created/updated/deleted

"Snapshot of all open issues nightly"

None of these — use a Scheduled webhook with JQL instead


What about Sprint, Board, Backlog events?

Webhooks Pro subscribes to Atlassian's avi:jira:* event taxonomy. Sprint and Board lifecycle events are exposed via avi:jira:* and surface on the relevant tabs as Atlassian releases them. If you don't see one you need, tell us at support@ux-software.com — we ship subscriptions to new event families when Atlassian publishes them.


What about the order of events?

Jira does not guarantee ordering between unrelated events. For the same entity (same issue), events arrive in source order, but with debounce a burst of edits collapses into one final delivery (see Debounce and coalescing).

If you need strict ordering across events on the receiver side, derive it from timestamp in the payload, not from delivery order.


Related