Triggers

Field value changed

  • Smart values: No
  • Available in server lite: No

Use this trigger to run an automation rule whenever a given field's value changes. Want to know when an issue's priority changed to Critical? Use this trigger with a compare condition!

Field value changed trigger


Incoming webhook

  • Smart values: No
  • Available in server lite: No

Quite often you need to integrate with other systems. Webhooks are becoming a common way for applications to talk. The trigger listens for a Webhook request and triggers a rule when it receives one. You can pass in a data to reference in later components or run a JQL to retrieve issues.

Incoming webhook trigger


Issue assigned

  • Smart values: No
  • Available in server lite: Yes

Rule is run when an issue is assigned to a user. The trigger needs no configuration.

Issue assigned trigger


Issue commented

  • Smart values: No
  • Available in server lite: Yes

Rule is run when a comment is added to an issue. The trigger needs no configuration.

Issue commented trigger


Issue created

  • Smart values: No
  • Available in server lite: Yes

Rule is run when an issue is created. The trigger needs no configuration.

Issue created trigger


Issue deleted

  • Smart values: No
  • Available in server lite: Yes

Rule is run when an issue is deleted. The trigger needs no configuration.

Issue deleted trigger


Issue linked

  • Smart values: No
  • Available in server lite: No
  • Minimum Jira version: Jira 7.5+

Rule is run when an issue is linked to another issue

Issue linked trigger


Issue moved

  • Smart values: No
  • Available in server lite: No

Rule is run when an issue is moved to the specified project.

Issue moved trigger


Issue property updated

  • Smart values: No
  • Available in server lite: Yes

This advanced trigger allows you to react to issue property changes in Jira Server. You can listen to changes for specific properties or all properties.

issue property updated trigger

TIP

Due to API limitations, this action is only available in Jira Server.


Issue transitioned

  • Smart values: No
  • Available in server lite: Yes

Rule is run when an issue is transitioned through its workflow. The trigger needs no configuration.

Issue transitioned trigger


Issue updated

  • Smart values: No
  • Available in server lite: Yes

Rule is run when an issue is updated/edited. The trigger needs no configuration.

Issue updated trigger


Manual

  • Smart values: No
  • Available in server lite: No

This trigger adds a panel to the view issue page that allows you to manually kick-off a rule. This is great for common tasks. You can restrict who can run/see this rule.

Manual trigger


Multiple issue events

  • Smart values: No
  • Available in server lite: Yes

Sometimes you may want to trigger the same rule when a number of different events occur. For example you may want to add the user that updated an issue to a custom field when an issue is updated, transitioned or assigned.

Multiple issue events trigger


Scheduled

  • Smart values: Yes (JQL)
  • Available in server lite: Yes

This executes a rule on the specified schedule. You can run the rule on a defined period or use a Cron expression for more complex schedules. You can choose to either run a JQL query or simply run the rule if you're trying to create issues on a schedule.

Scheduled trigger


Service limit breached

  • Smart values: No
  • Available in server lite: Yes

You can use this trigger to setup a rule to be notified when you are about to breach processing time limits defined in your Jira instance.

Service limit breached


SLA threshold breached

  • Smart values: No
  • Available in server lite: No
  • Minimum Jira version: Jira 7.3+ and Service Desk 3.3+

Want to execute a rule when a Jira ServiceDesk SLA breaches? Then this trigger is for you! You can execute a rule on breach, or when it's close to breaching (or has breached by more than a provided timeout).

SLA trigger

TIP

This trigger is only available in Jira ServiceDesk projects!


Sprint created, started or completed

  • Smart values: No
  • Available in server lite: No

These sets of triggers will run when a sprint is created, started or completed. You'll need to select a specific scrum board for this to run on.

A {{sprint}} object can be used as a smart value in later components.

You can also loop through all issues available in this sprint by using the related "Issue in the sprint" related issue block.

Sprint trigger


Version created, updated, released

  • Smart values: No
  • Available in server lite: No

You can configure a rule to run when a version is created, updated or released. Note that the updated trigger encompasses version being created and released, so you should only use it if you need to listen for all events around a version.

You can optionally restrict it to just versions that match a regular expression.

A {{version}} object can be used as a smart value in later components.

You can also loop through all issues fixed in this version by using the related "Issue fixed in version" related issue block.

Version trigger