
    Skip to main contentCloud automation SupportApps DocumentationResourcesContact usSign inSign inCloud automationDocumentationAutomation basicsKey conceptsImporting automation rules in an Atlassian Government environmentManage editors for your automation rulesUse automation components in a ruleWhat are rule details in Atlassian Automation?What are smart values?What are system rules in Atlassian Automation?What is a rule actor?What is rule branching?Configure automation rule groupsAdd conditions to an automation ruleBest practices for optimizing automation rulesMonitor automation activityAutomation service limitsWhat is an automation audit log?Audit the run logs of automation rulesDebug an automation ruleView performance insights for automation rulesHow is my usage calculated?Retry failed rules in Atlassian AutomationView your automation usageOrganize your rules with labelsUse automation with other applicationsWhat are connections in Automation?Connect your automation rule to another toolThird-party applications that connect to AutomationUse Ansible with AutomationUse AWS with Jira AutomationUse Confluence with Jira AutomationUse Docusign with AutomationUse Entra ID with AutomationUse GitHub with AutomationUse Jira Edge Connector (JEC) with Jira AutomationUse Microsoft Azure with Jira AutomationUse Microsoft Teams with AutomationUse New Relic with Jira AutomationUse Okta with AutomationUse Slack with AutomationUse Workato with AutomationUse Workday with AutomationConfigure AWS IAM for Jira AutomationConfigure AWS SNS for Jira AutomationConfigure the incoming webhook trigger in Atlassian AutomationAdd restrictions to automation componentsUse Amazon with AutomationUse Datadog with AutomationUse Docker with AutomationUse Focus with Jira AutomationsUse Jenkins with AutomationUse Jira Automation with Confluent KafkaUse Microsoft Azure with AutomationUse Splunk with AutomationUnavailable automation components in Atlassian Government CloudUse Google Cloud Platform actions with AutomationUse Google Cloud with AutomationConfluence Cloud automationManage automation in Confluence CloudCreate automation rules in ConfluenceEdit, copy, and delete automation rules in Confluence CloudSmart buttons for automation in ConfluenceComponents – Confluence automationTriggers in Confluence automationConditions in Confluence automationBranches in Confluence automationActions in Confluence automationSmart values – Confluence automationSmart values in Confluence automationJira Cloud automationGet started with Jira automationCreate and configure Jira automation rulesCreate and edit Jira automation rulesBranch automation rules to perform actions on related work itemsTest an automation rule using the Manual triggerEnable and disable Jira automation rulesRun Jira rules as another userTransfer Jira automation rules from one user to anotherImport and export Jira automation rulesCreate rules with Rovo in Jira automationIssue data (Automation format) payload for Send Web RequestIssue data (Jira format) payload for Send Web Request actionLimitations in team-managed projects for automation rulesPermissions required to manage automation rulesComponents in Jira automationJira automation actionsJira automation branchesJira automation conditionsJira automation triggersAdvanced automation componentsDifferences between Automation in Jira Server and Jira CloudSmart values in Atlassian AutomationAutomation smart values - issuesAutomation smart values - projectsAutomation smart values - listsAutomation smart values - text fieldsAutomation smart values - usersAutomation smart values - alertsAutomation smart values - conditional logicAutomation smart values - date and timeAutomation smart values - designAutomation smart values - developmentAutomation smart values - JSON functionsAutomation smart values - math expressionsAutomation smart values - securityAutomation smart values - AssetsAutomation smart values - Atlassian GuardAutomation smart values - Loom Automation smart values - Rovo agentsFind all available smart values for a Jira issueExamples of using math expression smart valuesExamples of using smart values with datesExamples of using smart values with listsExamples of using smart values with text stringsFormatting smart values in Jira automationUse smart values with rich text editing Use Jira automation rules to modify work itemsAdvanced field editing using JSONConvert usernames to account IDsConvert wiki markup to HTML or plain text in Jira automationEdit issue fields with Jira automationMove an issue to another project using automationSchedule work items to recur using automationsTransition a work item with automationAtlassian SupportResourcesJira Cloud automationComponents in Jira automationJira automation triggersEvery rule starts with a trigger. They kick off the execution of your rules. Triggers will listen for events in Jira, such as when a work item is created or when a field value is changed.Apply conditions directly to the trigger to add criteria to the entire rule. This will filter which triggers continue your automation.Triggers can be set to run on a schedule, and can be customized before being applied to a rule.See how to use all of these triggers in our Jira automation template library. General triggersThese triggers can be used across all Jira Cloud products.Field value changedRelated 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 a work item’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 narrow down the fields to monitor by specifying a change type: Value added, value deleted or any changes to the field value. You can also narrow down the work item operations that will trigger this rule – create, edit, transition or assign – or leave it blank to listen to all operations.Form attachedForm triggers are only space-specific and can’t be configured in globally. The rule will run whenever a form is manually attached to an existing work item, but also when a form is attached using the Add form API or a form is copied to another work item using the Copy form API. Form opened for editsForm triggers are only space-specific and can’t be configured in globally. The rule will run whenever a form is opened for customer edits on existing work items. For example, there may be times when an agent selects Open for edits on an already submitted form on a work item. This could be the trigger that sends a notification to a customer that they need to resubmit a form. This trigger will run whenever a form is manually opened for edits, but also when a form is opened using the Reopen form API.Form submittedForm triggers are only space-specific and can’t be configured in globally. The rule will run when forms attached to a work item are submitted. When configuring the trigger, you can select any number of forms, which will change how the trigger will act:If no forms are selected: the rule will run when any form is submitted.If one form is selected: the rule will run when that form is submitted.If multiple forms are selected: the rule will only run when all of the selected forms on a work item are submitted.Read more about form statesIncoming webhookRelated 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 work items to act on, or even provide real-time data you can use to update a work item.When configuring this trigger, you’ll receive a unique URL and secret that you can either 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 work item keys and other data.You can use the {{webhookData}} smart value to reference the custom XML data provided by the webhook in your rule.Work item assignedRelated smart values: {{assignee}}The rule will run when the Assignee of a work item is changed. For example, when a work item is assigned to a specific user, change the work item’s status to In progress and send an email to the reporter to let them know it’s being investigated.Work item commentedRelated 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 a work item. Choosing a comment type allows you to distinguish if a comment was added stand-alone, or as part of a transition. For example, you may want to set an automation rule where a comment added to a closed work item re-opens, or a comment added transitions the status of the work item. The available comment types are:All Comments (default): All comments that are added to a work item.Comment is the main action: New comment is added as a message in the comments section.Comment added during status transition: Comment is added when you change the status of a work item.Comment added while editing work item fields: Comment added while editing one or more work item fields.Editing a comment will not trigger this rule.Work item comment editedRelated smart values: {{comment}}This rule will run when a comment is edited. Can be used with the Edit comment action.Work item createdRelated smart values: {{issue}}The rule will run when an work item is created.You can use this trigger with actions to customize the new work item, including populating fields, assigning to users, and adding sub-tasks.Work item deletedRelated smart values: {{issue}}The rule will run when a work item is deleted. For example, send an email notification that a work item has been deleted.You can use conditions to refine exactly the work item you are monitoring.Work item linkedRelated smart values: {{destinationIssue}}, {{linkType}}The rule will run when a work item is linked to another work item.You can configure this trigger based on any link type.Work item link deletedRelated smart values: {{destinationIssue}}, {{linkType}}The rule will run when a work item is unlinked from another work item.You can configure the trigger to only execute for specified link types, or for all work item links.Work item movedRelated smart values: {{issue}}The rule will run when a work item is moved from one space 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 space.Work item transitionedRelated smart values: {{issue}}, {{changelog}}The rule will run when a work item 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 a work item with automationWork item updatedRelated smart values: {{issue}}The rule will run when the details on a work item are updated.Exceptions on this trigger include changes made by the Link work item, Assign work item and Log work actions.To trigger a rule when a work item’s status is updated, please use the Work item transitioned trigger instead.Manual trigger from work itemRelated smart values: {{issue}}The rule will run when it is manually triggered by a user. This trigger is useful for automating common tasks, or testing or debugging a rule. Learn more about using the Manual trigger to test rulesYou can refine which users can manually trigger a rule by selecting a permissions group in the Groups that can run trigger dropdown. Learn more about permission groupsYou can also request input before a rule is run by selecting Get input from users. This allows you to set up some fields that will display to users when they trigger the rule. You can choose to make each field mandatory by selecting Required field. If a user chooses not to enter any information and selects Cancel, this won’t count as an execution towards your monthly limits.Once a rule is created with a Manual trigger, anyone with access will be able to trigger it by going to a work item and selecting Actions. Multiple work item eventsRelated smart values: {{issue}}The rule will run when one or more selected work item events occur. For example, send a Slack message when a work item is updated, transitioned or assigned.Using this trigger may be easier and more efficient than creating several different rules.Space createdRelated smart values: Automation smart values – spacesRule will run when a space is created. For example, this could be useful if you want to create a set of default work items that should be included in all Jira spaces.ScheduledRelated smart values: {{issue}}This rule runs on a specified schedule. You can run the rule at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules.You can also choose to enter a JQL query. If you do, actions in this rule will execute on the work items included in the query.Scheduled rules that reach a Failure status for 10 consecutive executions will disable automatically.Work loggedRelated smart values: {{worklog}}This rule will run when a work log is created, updated and/or deleted.Software triggersThe following triggers are only available for Jira.Sprint created, started, or completedRelated 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 work items branch Work item fixed in version to loop through all work items fixed in this version.Version created, updated, releasedRelated 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 work items branch Work item fixed in version to loop through all work items fixed in this version.DevOps triggersThese triggers are only available for Jira Cloud when integrated with a source code management tool. Check out the list of compatible toolsSelf-hosted or On-Premise tools (e.g. Bitbucket Server, Gitlab On-Premise, Github Enterprise) aren't supported. Though they can still be integrated with Jira Cloud and you'll still get the benefits of integrating in other parts of your software space.Branch createdRelated smart values: {{branch}}Connect your source code management tool to use this trigger. Learn how to integrate your development tools with Jira Cloud.You can use conditions to refine the branches you are monitoring with this trigger. The rule will run when a branch is created. For example, when a branch is created that includes a work item key, transition that work item to In progress.Build failedRelated smart values: Smart values - developmentConnect your source code management tool to use this trigger. Visit the marketplace to integrate your build tool with Jira Cloud.Rule executes when a build fails. You can configure this rule to only trigger on certain build names, or builds associated with certain branches or tags.Build status changedRelated smart values: Smart values - developmentConnect your source code management tool to use this trigger. Visit the marketplace to integrate your build tool with Jira Cloud.Rule executes when the status of a build changes. You can configure this rule to only trigger on certain build names or builds associated with certain branches or tags.Build successfulRelated smart values: Smart values - developmentConnect your source code management tool to use this trigger. Visit the marketplace to integrate your build tool with Jira Cloud.Rule executes when a build succeeds. You can configure this rule to only trigger on certain build names or builds associated with certain branches or tags.Commit createdRelated 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 executes when a commit is created. You can use conditions to refine the commits you are monitoring with this trigger.Component created in CompassRelated smart values: {{component}} Read more about development smart valuesThe Component created in Compass trigger will cause your rule to run when a component is created in Compass.You must already have access to a Compass site in order to use this trigger. Discover CompassYou’ll be prompted to set up a connection to Compass the first time you use this component. Read more about connectionsScorecard status change in CompassRelated smart values: {{scorecard}} {{component}}The Scorecard status change in Compass trigger will cause your rule to run when a scorecard changes status in Compass. You must already have access to a Compass site in order to use this trigger. Discover CompassYou’ll be prompted to set up a connection to Compass the first time you use this component. Read more about connectionsDeployment failedRelated smart values: Smart values - developmentConnect your source code management tool to use this trigger. Visit the marketplace to integrate your deployment tool with Jira Cloud.Rule executes when a deployment fails.Deployment status changedRelated smart values: Smart values - developmentConnect your source code management tool to use this trigger. Visit the marketplace to integrate your deployment tool with Jira Cloud.Rule executes when the status of a deployment changes.Deployment successfulRelated smart values: Smart values - developmentConnect your source code management tool to use this trigger. Visit the marketplace to integrate your deployment tool with Jira Cloud.Rule executes when a deployment succeeds.Pull request createdRelated 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 executes when a pull request is created. You can use conditions to refine the pull requests you are monitoring with this trigger. For example, when a pull request is created that includes a work item key, transition that work item to In review.Pull request declinedRelated 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 executes when a pull request is declined. You can use conditions to refine the pull requests you are monitoring with this trigger.Pull request mergedRelated 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 executes when a pull request is merged. You can use conditions to refine the pull requests you are monitoring with this trigger.Security triggersVulnerability foundRelated smart values: {{vulnerability}}Connect a security tool to your space to use this trigger. Learn more about integrating security toolsRule is run when a vulnerability in one of your connected security containers is found by your security tool and sent to Jira.Only vulnerabilities that match a severity you choose will activate the rule, you can choose one one or more severities in the trigger.Jira Service Management triggersAlert createdRelated smart values: {{alert}}The rule will run when an alert is created. You can use this trigger to perform actions on Jira Service Management when an alert is created.For example, create an incident in Jira Service Management when an alert is created or associate the alert with an ongoing incident. Manual trigger from alertRelated smart values: {{alert}}The rule is run when it is manually triggered by the user from Actions on an alert. For example, run an SSM document if the alert description contains certain keywords when the user manually triggers the rule.Users that can rule this rule: By default, your rule can be run by all logged-in users, but you can allow only specific users and members of a team to run your rule.Filter alerts to show this rule: You can make your rule available to be run only for certain alerts by choosing alert fields to filter by.Optionally, you can select Prompt for input when the rule is triggered if you want the user, who triggers the rule from an alert, to input any information before the rule is run. Alert updatedRelated smart values: {{alert}}The rule is run when an alert’s priority, summary, or description is updated. For example, create an incident of P3 priority in a service space when an alert’s priority changes to P1. Alert status changedRelated smart values: {{alert.status}}The rule will run when an alert’s status changes. For example, send a message to a Slack channel when an alert’s status changes to OPEN.  Alert note addedRelated smart values: {{alert.note}}The rule will run when a new note is added to an alert. For example, send an email when a note is added to an alert. Object triggerFor Jira Service Management only. Rule is run when an object from a specific Assets schema is created, updated, or deleted. This can only be used for global automation rules.Learn more about Assets in Jira Service Management Attribute value changedRelated smart values:{{attributeChangelog.(attribute name).from}}{{attributeChangelog.(attribute name).to}} {{attributeChangelog.(attribute name).changeType}} {{containerObject.(attribute name)}}For Jira Service Management only. Rule is run when the selected attribute changes on any object of this type. This can only be used for global automation rules.Learn more about Assets in Jira Service ManagementService limit breachedRelated smart values: {{breachedSummary}}, {{breachedRules}}The rule will run when the daily or hourly processing time service limit is about to be breached (note that it doesn’t monitor other types of services limits, such as the “Items queued globally” limit). Read more about automation service limitsSLA threshold breachedRelated smart values: {{issue}}The rule will run when a Jira Service Management SLA has breached 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.Approval requiredFor Jira Service Management only. Rule is run when a work item that requires approval is created or updated, or when new approvers are added to a work item. Learn more about approvals in Jira Service Management. Approval completedFor Jira Service Management only. Rule is run when an approval step on a work item is accepted or declined. Learn more about approvals in Jira Service Management.Emoji reaction to Slack messageRule is run when a user reacts with an emoji to the work item created by Assist in Slack.Currently, the trigger works only with work item messages created by the Atlassian Assist app in Slack channels. Learn more about chatSince this trigger uses the Slack workspace and channels you set up in chat settings, it won’t work unless you connect this service space to a Slack workspace and channel. Learn how to set up chat in Slack Design triggersDesign linked to work itemThe rule will run when a new Figma design is linked to a work item. Learn how to integrate Figma with JiraYou can use this trigger to add a DESIGN-LINKED label to the work item, and notify the assignee that a design has been added.Linked design updatedThe rule will run when a design already linked to a work item is updated.You can use this trigger to notify the assignee that a design has been updated.Status of a linked design changesThe rule will run when the status of a design that’s already linked to a work item changes.You can use this trigger to notify the assignee when a design status has changed, automatically add a status label, or transition the work item to the next status.A design needs to already be linkedThis rule will not run if you’re trying to link a new design to a work item, even if the from or to statuses are blank.Atlassian Guard triggersContent scanning alert for JiraThis trigger runs your rule whenever a content scanning alert is generated. Guard Detect generates an alert when someone updates a Jira work item containing certain types of sensitive data, such as credentials, financial, or identity data.To configure this trigger you need to be an Organization admin or Guard Detect admin and your organization must have an Atlassian Guard Premium subscription. Loom triggersLoom moved to folderRelated smart values: {{loomVideo}}This trigger runs your rule when a Loom video is moved to a Loom folder.Loom moved to spaceRelated smart values: {{loomVideo}}This trigger runs your rule when a Loom video is moved to a Loom space.Loom records meetingRelated smart values: {{loomVideo}}This trigger runs your rule when a meeting(s) is recorded by Loom.Was this helpful?YesNoIt wasn't accurateIt wasn't clearIt wasn't relevantProvide feedback about this articleStill need help?The Atlassian Community is here for you.Ask the CommunityComponents in Jira automationShow moreJira automation branchesJira automation conditionsJira automation triggersAdvanced automation componentsDifferences between Automation in Jira Server and Jira CloudOn this pageGeneral triggersField value changedForm attachedForm opened for editsForm submittedIncoming webhookWork item assignedWork item commentedWork item comment editedWork item createdWork item deletedWork item linkedWork item link deletedWork item movedWork item transitionedWork item updatedManual trigger from work itemMultiple work item eventsSpace createdScheduledWork loggedSoftware triggersSprint created, started, or completedVersion created, updated, releasedDevOps triggersBranch createdBuild failedBuild status changedBuild successfulCommit createdComponent created in CompassScorecard status change in CompassDeployment failedDeployment status changedDeployment successfulPull request createdPull request declinedPull request mergedSecurity triggersVulnerability foundJira Service Management triggersAlert createdManual trigger from alertAlert updatedAlert status changedAlert note addedObject triggerAttribute value changedService limit breachedSLA threshold breachedApproval requiredApproval completedEmoji reaction to Slack messageDesign triggersDesign linked to work itemLinked design updatedStatus of a linked design changesAtlassian Guard triggersContent scanning alert for JiraLoom triggersLoom moved to folderLoom moved to spaceLoom records meetingCommunityQuestions, discussions, and articlesAccessibilityNotice at CollectionPrivacy PolicyTerms of UseSecurity2026 Atlassian


document.body.addEventListener(
    "error",
    (event) => {
        if (!event.target) return;

        if (event.target.tagName === "SCRIPT") {
            Sentry.captureMessage(
                "Failed to load script: " + event.target.src,
                "warning"
            );
        }
    },
    true // useCapture - necessary for resource loading errors
);

This site uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. To change your preferences, click Manage preferences. Otherwise, clicking Accept all cookies indicates you agree to our use of cookies on your device. Clicking Reject all cookies means you do not agree to our use of non-strictly necessary cookies on your device.Atlassian Cookies and Tracking NoticeManage preferences Reject all cookies Accept all cookiesManage PreferencesWhen you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
            More informationAccept allStrictly Necessary CookiesAlways ActiveThese cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.Targeting Cookies  Targeting Cookies InactiveThese cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.Functional Cookies  Functional Cookies ActiveThese cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.Performance Cookies  Performance Cookies ActiveThese cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.Back ButtonCookie List Search IconFilter IconClear checkbox label labelApply CancelConsent Leg.Interest checkbox label label checkbox label label checkbox label labelReject all Confirm my choices
