Every rule starts with a trigger. They kick off the execution of your rules. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed.

Triggers can be set to run on a schedule, and can be customized before being applied to a rule.

Branch created

  • Related smart values{{branch}}

Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The rule will run when a branch is created. For example, when a branch is created that includes an issue key, transition that issue to In progress.

You can use conditions to refine the branches you are monitoring with this trigger.


Commit created

  • Related smart values: {{commit}}

Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The rule will run when a commit is created.

You can use conditions to refine the commits you are monitoring with this trigger.


Field value changed

  • Related smart values{{fieldChange}}

The rule will run when a field value is changed. All system and custom fields are supported by this trigger.

You can use this trigger together with conditions to check the value of fields before performing actions. For example, send an SMS when an issue’s priority changes to greater than high.

When configuring this rule, you can select the fields to monitor for change, or use a regex to match the field names. You can also narrow down the issue operations that will trigger this rule – create, edit, transition or assign – or leave it blank to listen to all operations.


Incoming webhook

  • Related smart values{{webhookData}}

The rule will run when a HTTP POST is sent to a specified webhook URL.

A webhook is a way for a third-party to trigger an automation rule. The webhook can specify issues to act on, or even provide real-time data you can use to update an issue.

When configuring this trigger, you’ll receive a unique URL that you can wither add to the third-party application’s outgoing webhook configuration, or make a HTTP POST request from your custom scripts. The trigger also provides details on how to provide issue keys and other data.

You can use the {{webhookData}} smart value to reference the custom data provided by the webhook in your rule.


Issue assigned

  • Related smart values{{assignee}}

The rule will run when the Assignee of an issue is changed. For example, when an issue is assigned to a specific user, change the issue’s status to In progress and send an email to the reporter to let them know it’s being investigated.


Issue commented

  • Related smart values{{comment}}

The rule will run when a new comment is added. For example, change the status to In progress when a new comment is added on an issue.

Editing a comment doesn’t will not trigger the rule.


Issue created

  • Related smart values{{issue}}

The rule will run when an issue is created.

You can use this trigger with actions to customize the new issue, including populating fields, assigning to users, and adding sub-tasks.


Issue deleted

  • Related smart values{{issue}}

The rule will run when an issue is deleted. For example, send an email notification that an issue has been deleted.

You can use conditions to refine exactly the issue you are monitoring.


Issue linked

  • Related smart values{{destinationIssue}}{{linkType}}

The rule will run when an issue is linked to another issue.

You can configure this trigger based on any link type.


Issue link deleted

  • Related smart values{{destinationIssue}}{{linkType}}

The rule will run when an issue is unlinked from another issue.

You can configure the trigger to only execute for specified link types, or for all issue links.


Issue moved

  • Related smart values{{issue}}

The rule will run when an issue is move from one project to another.

You can use this trigger together with conditions and actions to ensure all values, fields and settings are copied across to the new project.


Issue transitioned

The rule will run when an issue transitions from one status to another.

You can configure this trigger so it listens to the status of your choice, or simply any transition in your workflow.

Learn more about transitioning an issue with automation.


Issue updated

  • Related smart values{{issue}}

The rule will run when the details on an issue are updated.

Exceptions on this trigger include changes made by the Link issueAssign issue and Log work actions.


Manual

  • Related smart values{{issue}}

The rule will run when it is manually triggered by a user.

You can refine which groups can manually trigger a rule. This trigger is useful for automating common tasks, or testing or debugging a rule.

Learn more about manually running rules.



Multiple issue events

  • Related smart values{{issue}}

The rule will run when one or more selected issue events occur. For example, send a Slack message when an issue is updated, transitioned or assigned.

Using this trigger may be easier and more efficient than creating several rules.


Pull request created

  • Related smart values{{pullRequest}}

Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The rule will run when a pull request is created. For example, when a pull request is created that includes an issue key, transition that issue to In review.

You can use conditions to refine the pull requests you are monitoring with this trigger.


Pull request declined

  • Related smart values{{pullRequest}}

Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The rule will run when a pull request is declined.

You can use conditions to refine the pull requests you are monitoring with this trigger.


Pull request merged

  • Related smart values{{pullRequest}}

Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.

The rule will run when a pull request is merged.

You can use conditions to refine the pull requests you are monitoring with this trigger.


Scheduled

  • Related smart values{{issue}}

This rule runs on a specified schedule.

You can run the rule at a fixed rate, or use a Cron expression for more complex schedules. You can choose to run a JQL query, or simply run the rule if you’re creating issues on a schedule.


Service limit breached

  • Related smart values{{breachedSummary}}, {{breachedRules}}

The rule will run when your service limit has or is about to breach.

You can use this trigger to monitor your service limits and be notified when you may be approaching them.


SLA threshold breached

  • Related smart values{{issue}}

This trigger is only available in Jira Service Desk projects.

The rule will run when a Jira Service Desk SLA has or is about to breach.

This trigger allows you to provide timely feedback to customers, alert agents, and automatically prioritize requests accordingly. You can select the SLA to monitor, and the time before or after it has breached to trigger.


Sprint created, started or completed

  • Related smart values{{sprint}}

The rule will run when a sprint is created, started or completed on the selected scrum board.

This trigger will either run for every sprint on that board, or you can narrow this down using a regular expression.

You can use this trigger together with the related issues branch Issue fixed in version to loop through all issues fixed in this version.


Version created, updated, released

  • Related smart values{{version}}

The rule will run when a version is created, updated or released.

You can restrict which versions will trigger this rule using a regular expression.

The Version updated trigger listens for versions being created and released, as well as being amended. Use this trigger if you need to listen for all events around a version.



You can use the Version released trigger together with the related issues branch Issue fixed in version to loop through all issues fixed in this version.

Work logged

  • Related smart values{{worklog}}

This rule will run when a work log is created, updated and/or deleted.