{{deletedFieldChanged.values}} - Returns the value/values deleted. You can specify a default value to prevent this. Examples of using smart values with dates. Learn more about date smart values. [property]}} @Daniel Ramotowski, more people seem to be interested in this functionality, as there was already a ticket open forhttps://jira.atlassian.com/browse/JIRAAUTOSERVER-212 ! These smart values can only be accessed through other root keys (e.g{{deployment.environment}}). The trigger for automation is starting a new sprint (trigger = start sprint). On successful request, you will be able access webhook response data using the available smart values. A repository represents a collection of files and associated metadata. Your smart value must identify a specific attachment for this to work. They can add significant power and complexity to your rules. Create and configure Jira automation rules, Branch automation rules to perform actions on related issues, Issue data (Automation format) payload for Send Web Request, Issue data (Jira format) payload for Send Web Request action, Limitations in team-managed projects for automation rules, Permissions required for Jira Cloud automation rules, Test a Jira automation rule using the Manual trigger, Transfer Jira automation rules from one user to another, Differences between Automation in Jira Server and Jira Cloud, Examples of using math expression smart values, Examples of using smart values with dates, Examples of using smart values with lists, Examples of using smart values with text strings, Use Jira automation rules to modify issues, Convert wiki markup to HTML or plain text in Jira automation, Move an issue to another project using automation, Learn how to use these to interact with Jiras REST API. You can check this by navigating to the "Custom fields" page in theglobal admin section. Used with: the Create feature flag in LaunchDarkly action. For more information on when issues is available, see, Multiple comments on the active issue (this example is explained in detail in, Properties for versions include:name, description, archived, released, releaseDate, "Customer Request Type" in older instances of Jira. We select the exact field we are listening out for, in this case story points. For example if a rule has both a Create branch in GitHub action and a Create branch in GitLab action, the details of the most recent branch will be returned. And we have lots more automation templates and guides for you to use and learn from in the automation template library. See all smart values related to Assets in Jira Service Management Cloud. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. They allow you to automate tasks and make changes within your site. Learn more about using smart values with sections and lists. {{changelog.issuetype}} - Changelog information for theIssue type field. https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}. Accesses information for the version that triggered the rule. Automation is currently available in Jira Software Cloud and Confluence Cloud. Note that repository contains additional nested smart values. Available only for the pull request created trigger. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. You can check this by navigating to the "Custom fields" page in the. The smartvalue{{webhookData}}gets the root of the JSON payload. A pull request represents proposed changes before they are integrated into an official project. {{issue.comments.author.displayName}} - Returns the comment authors. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. Jira smart values in automation rules. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. It resets every quarter so you always have a chance! In the following example, we list each comment that an issue has, and include the author and creation date/time: In this example, we return the name of the person who added the last comment on an issue: Used to access the values in an issue's Components field. This is more than enough for the interfce to update the issue over API and when it is finished, my automation will jump in and continue. Acording with the documentation, Automation JQL condition suport smart values. {{createdBranches.repository}} - accesses details of the branches' repositories, {{createdBranches.repository.id}} - returns the IDs of each repository, {{createdBranches.repository.name}} - returns the names of each repository. For more information on when issues is available, seeRun a rule against issues in bulk. The rule is running too quickly after the issue is created. To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. The status of a rule can be seen on its details screen. The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. {{branch.repository.url}} returns the URL, e.g. Is the IF statement available for Server version? They are using the curly-brace syntax like { {someSmartValue}} . I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. This smart value accesses the changelog, and a list of changes for each field. Learn more about using smart values with sections and lists. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. {{issue.epic. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. [Custom Field].name}} - Returns the visible label displayed on the left of the field. Issue commented, Added by: Clone Issue Action, Create Issue Action, Create Sub-tasks Action, A list of issues that have been created in the rule, The type of event that triggered the rule such as: jira:issue_updated :issue_commented. I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). Otherwise, register and sign in. We do not currently support accessing fields within insight objects. In this case, we want to perform an action on the parent of the sub-task so in the dropdown menu, we choose Parent. If multiple values are changed, use # to iterate over these. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. Can be combined with other user smart values. {fieldChange.toString}}- Returns the new value as displayed. {{rule.name}} - Returns the name of the rule that is currently running. A good tip for checking your progress is to say aloud what you have built so far: Whenever the field value changes for story points AND it is a sub-task. To get a property in it, we should use{{webhookData.someValue.childValue}}. {{createdBranches.name}} - returns the names of the branches, {{createdBranches.url}} - returns the URLs of the branches. You could then use this to count the number of issues returned. Do more to earn more! Smart values are one of the most potent ways to do so. {{changelog.status}} - Changelog information for theStatus field. Actions are the doers of your rule. {{issue.created}} - Returns the issue's creation date. Used to access the values in an issue'sFix Versionsfield. Affects version of an issue as a list. {{issue.TempoAccountField}} - Returns the name of the account, {{issue.TempoAccountField.id}} - Returns the ID of the account, {{issue.TempoAccountField.name}} - Returns the name of the account, {{issue.TempoAccountField.value}} - Returns the name of the account, Can be used with: the Approval required trigger and the Approval completed trigger. If a condition fails, the rule will stop running and no actions following the condition will be performed. You can access all fields of the Epic. {{issue.affectedServices.name}} - Returns the names of the issue's Affected services. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. {{createdBranch.repository.url}} - returns the repositorys URL. View topic Find the smart value for a field Learn how to find the right Jira automation smart values for your issue fields in Jira Cloud. Join the Kudos program to earn points and save your progress. I am glad to learn that helped you. Hi John, thanks a lot for your quick response. Find issues that have the same custom field date as trigger issue. Each of your rules will have an audit log that you can review to see when the rule was triggered, the final result of the execution, and any actions that may have been performed. Field value changed Available in Server Lite: No for a select field. Share the love by gifting kudos to your peers. Properties are frequently used by add-ons and integrations to store values, e.g. Learn more about automation triggers. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. These can be combined with other user smart values. However sometimes the two fields holds the same p. {{pullRequest.sourceBranch}} returns information related to the source branch for the pull request. Triggers can be set to run on a schedule, and can be customized before being applied to a rule. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. Understand the general concepts and best practices of automation in Atlassian Cloud products. Accesses the previous issue created in the rule. When we use this trigger, we can use the {{webhookData}} smart value to represent the POST payload - we'll focus on this here. Also provides the customer portal URL forJira Service Management requests. {{pullRequest.destinationBranch}} returns information related to the destination branch of the pull request. {{approval.decision}} - Returns the final decision of the approval. {{commit.hash}} returns the SHA1 hash of the commit, e.g.4877576951f3eda43625d3345058e702dad3df0d. Learn more about configuring time tracking. First, you need a sample from the webhook payload data. Because this smart value deals with multiple items (i.e: issues can have many fix versions), it can be used with the#symbol to apply the rule to each individual fix version. Jira smart values - issues To test what your smart value returns, use the manual trigger with log action and the result displays in the audit log. Used with: any triggers that edit an issue. You can find some automation templates to help you get started within the product library. {{version.name}} - Returns the version's name. You can check this by navigating to the "Custom fields" page in theglobal admin section. You can access all fields of the Epic. 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 manually, based on a condition you set or scheduled. {{issue.description}} - Returns the content in the issue'sDescriptionfield. {{createdBranch.name}} - returns the name of the branch, {{createdBranch.url}} - returns the URL of the branch. Learn more about automation triggers. The URL to access the issue. Learn more about using smart values with sections and lists. {{version.project.key}} - Returns the project key of the project the version belongs to. For example, if the Assignee of a field changes, you could add a comment to the issue to note who the previous assignee was, and who the new assignee is. {{webhookResponse.status}} - response code e.g. Used with the Version created, Version updated, and Version released triggers. TEST-123-some-feature, {{pullRequest.sourceBranch.url}} returns the URL of the source branch, e.g.https://bitbucket.org/account/repo/TEST-123-some-feature. Used with: the Clone issue, Create issue, and Create sub-tasks actions. General triggers These triggers can be used across all Jira products.