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 build is processed.
Currently, it is not possible for apps to provide custom triggers for Automation for Jira rules. We would really like to implement app-specific triggers that would remove the need to copy&paste information and improve the overall integration experience. If this is something you would like to see as well, then please vote on FRGE-1558
You can use some of the official triggers (listed below), but those will require that you copy&paste curtain configuration values instead of being able to select them.
Webhook Trigger
Rule executed when an event is received that has one or more webhook configurations associated with it. See trigger documentation for more details on how to configure incoming webhooks on your rules.
Data related to the event is available in the webhookData smart value, see
webhook data documentation.
Once you have a rule configured to trigger on a webhook, you can use webhook automations to trigger the rule on specific events from the app.
Build Failed (Official)
Rule executes when a build fails. You can configure this rule to only trigger on certain build names. See trigger documentation for more details.
Build Status Changed (Official)
Rule executes when the status of a build changes. See trigger documentation for more details.
Build Successful (Official)
Rule executes when a build succeeds. You can configure this rule to only trigger on certain build names. See trigger documentation for more details.
Deployment Failed (Official)
Rule executes when a deployment fails. See trigger documentation for more details.
Deployment Status Changed (Official)
Rule executes when the status of a deployment changes. See trigger documentation for more details.
Deployment Successful (Official)
Rule executes when a deployment succeeds. See trigger documentation for more details.
Previous: Automation
Next: Actions
