Listeners
Last updated 24/08/2026
Listeners run a script automatically when something happens in Jira. Ten kinds:
Kind | Fires when… |
|---|---|
onCreate / onUpdate / onDelete / onAssign | A work item is created, updated, deleted, or its assignee changes. |
onComment | A comment is added or edited ( |
onWorklog | A worklog is created/updated/deleted (branch on |
onLink / onAttachment | A work item link or attachment is created/deleted. |
onVersion | A project version is created/updated/released/unreleased/archived/deleted. |
Scoping
Each listener can be limited with searchable pickers loaded live from your Jira: Projects, Work item types, and (for onUpdate) Changed fields. Empty pickers match everything. Filters fail open: if an event doesn't carry enough data to evaluate a filter, the hook still runs — scoping can never silently kill it.
“Assigned to a Team”? Jira Cloud has no team-assignment event — a team change is an onUpdate whose changelog includes the Team field. Scope an onUpdate listener to the Team changed field.
Example
// kind = onCreate — comment on every newly created work item
const key = context.event.issue.key;
await jira.addComment(key, 'Thanks! Triage checklist: severity, component, steps.');
return {{ commented: key }};