Jira trigger
Starts the automation on a Jira event for a chosen project. In the trigger picker it is Jira, under Integration Triggers.
Fields
| Field | Required | Description |
|---|---|---|
| Connection | Yes | The Jira connection to use. |
| Project | Yes | The Jira project to watch. |
| JQL Filter | No | A refinement combined with the project filter—for example priority in (High, Highest) or assignee = currentUser(). |
| Event | Yes | The event to fire on. |
Events
| Event | Fires when | Its own fields |
|---|---|---|
| Issue Created | An issue is created. | — |
| Issue Updated | An issue changes. | Changed Fields—fire only when one of the listed fields changed. Leave it empty to match every update. |
| Issue Deleted | An issue is deleted. | — |
| Comment Added | A comment is added. | — |
| Comment Updated | A comment is edited. | — |
Registering the webhook
Jira has to be told to send these events. With an OAuth connection that registration happens automatically when you save the trigger. With an API token connection an administrator sets the webhook up by hand, because Atlassian limits its dynamic-webhook endpoint to OAuth apps. The node shows the current setup status either way.
Output
The event's payload—the issue or comment involved.