
    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 conditionsYou can specify conditions that must be met for your rule to continue running. For example, your rule will only escalate an issue if it is high priority.Conditions can be placed anywhere in the rule chain. If a condition fails, no actions following it will be performed. The exception is with the If/else block condition. Not all rules need to have conditions.The location of conditions on a rule will affect how they work.Issue fields conditionUse smart values here: NoChecks whether an issue field meets a certain criteria.This condition doesn’t require you to write smart values or JQL, and supports most common Jira fields. Use this condition ahead of the JQL and Advanced compare conditions, where possible.There are multiple ways to use this condition:Compare a field with another valueCompare a field with another fieldAlert fields conditionUse smart values here: NoChecks whether an alert’s field meets a certain criteria. For example, you can use this condition to execute the action only if a new alert’s description includes the keywords you specify.You can group multiple conditions using Any/All option in If/else block. This condition can be used only with alert triggers because an alert is required for this condition to work. {{smart values}} conditionUse smart values here: YesCompares two values, using smart values and regular expressions.While the Issue fields condition will meet most needs, this condition provides extra options, such as the use of regular expressions and functions.For example, if you wanted to re-open an issue when a customer comments, you would start with the Issue commented trigger. You could then add this condition to compare the comment’s author with the issue reporter, and add another condition to check if the issue status is Done. Once these conditions are satisfied, the issue will transition to In progress.The comparison methods available are:Equals (e.g. the assignee equals John)Does not equal (e.g. the assignee does not equal John)Greater than (e.g. the number of watchers is greater than 5)Less than (e.g. the number of comments is less than 1)Starts with (e.g. the reporter's name starts with J)Contains (e.g. the summary contains December)Does not contain (e.g. the summary does not contain December).Contains regular expressionExactly matches regular expressionDoes not match regular expressionAffected servicesChecks if an issue’s affected services field matches the set criteria.You can configure this condition to check against the service tier, services name or dependent services of the affected services.This condition is only available on IT Service Management projects, for issues types that contain an affected services field type.Forms attachedNote that Form-related components are project-specific, so they can’t be configured in Global automation. Form components are only available in project automation.Checks if an issue has forms attached. You can check for multiple forms, and specify the status of the forms.Learn more about form states.If/else blockPerforms alternate actions based on whether certain conditions match or don’t match.This powerful condition allows you to add as many if/else conditions as you want. The if block executes the specified actions within that block when all the set conditions are met. If the conditions are not met, the else blocks will be evaluated. We support two levels of nesting with the if/else block.Issue attachmentsUse smart values here: NoChecks if the comment or description fields of an issue contains attachments.For example, you may want to check whether a customer has included a screenshot, or if a vendor has included an invoice – if there are no attachments, you could leave an automated comment requesting more information.You can combine this condition with the JQL condition to check if the filename of a specified format. You can also include a conditional compare on some properties of your attachments, including:filename {{attachment.filename}}: the filename of the attachmentmimeType {{attachment.mimeType}}: the file format of the attachmentauthor {{attachment.author}}: the user who added the attachmentaccountId {{attachment.author.accountId}}: the ID associated with the user nameemailAddress {{attachment.author.emailAddress}}: the email address associated with the user namedisplayName {{attachment.author.displayName}}: the name displayed in your Jira instanceactive {{attachment.author.active}}: Is the user an active user or has their account been deactivatedtimeZone {{attachment.author.timeZone}}: what timezone the user is registered being in (this does not change dynamically based upon where the user logs in from, it is the timeZone registered in their user account)created {{attachment.created}}: the date and time the attachment was added to the issuesize {{attachment.size}}: the attachment file size in bytesLearn more about attachment smart values.Issue has design linkedChecks if a Figma design is linked to an issue. The rule under the condition will only run if a design is linked. If there's no design linked to the issue, the rule (or branch of the rule) will not run.Learn how to integrate Figma with JiraAQLFor Jira Service Management only. Learn more about Assets in Jira Service Management. This condition checks if an Assets object or an issue's Assets field matches the AQL query.You can either search based on objects, or Assets fields on an issue. To select the Object tab, your rule must have the Object trigger. If the rule is triggered by an issue, the Issue field tab will be pre-selected and if the rule is triggered by an object, then the Object tab will be pre-selected.After entering an AQL query, you can select Validate syntax to check if the syntax of your query is valid. However, this doesn't check if the query will return results.You can also include object smart values, i.e. {{object name.attribute name}} in your query. Learn more about smart values for Assets in Jira Service ManagementJQLUse smart values here: YesBefore getting started with a JQL condition, check if you can use the Issue fields condition for your rule instead. It is easier and quicker to set up.Checks to see if an issue matches a specified JQL query.For example, checking that the status category of a status for a given issue is Done.statusCategory = DoneClick Validate query on this condition to check that your JQL query is working correctly. Note that:The issues found here may not be the same as the issues found when the rule runs. This is because the issues found when you select Validate query will be based on your permissions, but when the rule runs, it will use the rule actor’s permissions instead. If you’re using smart values, you won’t be able to check if your JQL is valid using Validate query.Related issuesUse smart values here: NoChecks if related issues exist on the trigger issue (e.g. parent, sub-tasks, epics, stories, etc.) or matches a specified JQL query.UserUse smart values here: Yes (Criteria)Checks whether a user exists or is in a specified group.You can add additional criteria to this condition, and select the logic of whether all or any of the criteria must be matched.For example, before reopening an issue, you could check if the user who added a comment to the issue is the reporter of the issue OR is a member of the participants custom field.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 automationJira automation actionsJira automation branchesJira automation conditionsJira automation triggersAdvanced automation componentsShow moreOn this pageIssue fields conditionAlert fields condition{{smart values}} conditionAffected servicesForms attachedIf/else blockIssue attachmentsIssue has design linkedAQLJQLRelated issuesUserCommunityQuestions, discussions, and articlesAccessibilityYour Privacy ChoicesPrivacy 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
