Rule Components Library
In Automation for Jira a rule is made up components that are chained together. We've got an ever growing library of components that can be combined together to create powerful rules.
Add Service Desk customer*
Comment on issue
Create Service Desk request*
Log a message
Send HipChat message
Send Slack message
Send Twilio notification
*...Available in Cloud only **...Available in Server only
Delete issue action
Sometimes you just need to get rid of some pesky issues automatically!
Publish event (Server only)
An advanced action to allow you to publish Jira events (system or custom) that other add-ons and integrations can listen for.
Find related issues for the issue that triggered the rule such as sub-tasks or stories in an Epic. This component will then allow you to create a parallel rule chain that will execute just for these related issues!
Send Webhook Action
Quite often you need to integrate with other systems. Webhooks are becoming a common way for applications to talk. This action allows you send an out bound Webhook to notify another system when this rule is run. You can also include the issue in the request.
Field value changed trigger
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!
Incoming Webhook Trigger
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.
Issue Assigned Trigger
Rule is run when an issue is assigned to a user. The trigger needs no configuration.
Issue Commented Trigger
Rule is run when a comment is added to an issue. The trigger needs no configuration.
Issue Created Trigger
Rule is run when an issue is created. The trigger needs no configuration.
Issue Deleted Trigger
Rule is run when an issue is deleted. The trigger needs no configuration.
Issue Moved Trigger
Rule is run when an issue is moved to the specified project.
Issue Property updated (Server only)
This advanced trigger allows you to react to issue property changes in Jira Server. You can listen to changes for specific properies or all properties.
This rule 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.
Multiple issue events trigger
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.
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.
Issue Attachments Condition
Allows you to check whether a field has any attachments or not.
This condition checks to see if the issue matches the specified JQL
Allows you check a specified user exists or is in a specified group.
Related Issues Condition
This condition can interate over a number of related issues and check, if all, some or none match a given JQL query.