Jira – Triggers

Estimated reading time: 8 min
Marketing icon jira 1 Jira - Triggers

What will start your automation…

These Triggers will start your Flow automatically at a specific time or intervals instead of being triggered by events like Webhooks.




The Flow will automatically start upon receiving a Webhook event, eliminating the need for a scheduler. It will continue running until you manually deactivate it.

Configuration Table:

(*) required field

Description*This is the label you give to the Trigger. It helps you identify it later inside the Flow.
Connection*This is the connection that Wiresk will use to register the webhook.
If the connection is not valid or not authenticated, the webhook cannot be created. Refer to how to create a connection.
API Key*Select or Create an API Key for authenticating the Webhook request.

PARAMETERS

Jira JQL Filter*:

The JQL filter that specifies which issues the webhook is sent for. Only a subset of JQL can be used. The supported elements are:

  • Fields: issueKeyprojectissuetypestatusassigneereporterissue.property, and cf[id]. For custom fields (cf[id]), only the epic label custom field is supported.”.
  • Operators: =!=IN, and NOT IN.

Jira Events*:

Multiple choices events:

  • Issue Created
  • Issue Updated
  • Issue Deleted
  • Comment Created
  • Comment Updated
  • Comment Deleted
  • Issue Property Set
  • Issue Property Deleted

Jira Field IDs Filter

A list of field IDs.

When the issue changelog contains any of the fields, the webhook jira:issue_updated is sent.

If this parameter is not present, the app is notified about all field updates.

Jira Issue Property Keys Filter

A list of issue property keys.

A change of those issue properties triggers the issue_property_set or issue_property_deleted webhooks.

If this parameter is not present, the app is notified about all issue property updates.