OMGYou're right. {{pullRequest.sourceBranch}} returns information related to the source branch for the pull request. They kick off the execution of your rules. For smart values related to the Insight feature in Jira Service Management, see Jira smart values - Assets. Learn more about list smart values. {{attachment.created}}: Returnsthe date and time the attachment was added to the issue. Check out how we use smart values in our Jira automation template library. These can be combined with other date and time smart values. For example if a rule has both a Create branch in GitHub action and a Create branch in GitLab action, {{createdBranches}} will return the values of both branches as a list. They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. [xxx].size}}: Returnsthe file size of a specific attachment. The status of a rule can be seen on its details screen. Through the dot notation you can access fields like issue type, status and custom fields (details on how you can use these to interact with Jira's REST api are, A list of issues generated by a trigger that runs a JQL search (, trigger when set to process in bulk). {{issue.affectedServices.changeApprovers}}, {{issue.affectedServices.changeApprovers.displayName}}, {{issue.affectedServices.dependentServices}}, {{issue.affectedServices.dependentServices.tier}}, {{issue.Request Type.currentStatus.status}}, {{comment.properties. {{versions.description}}- Returns the description of the affects version. {{deletedFieldChanged.values}} - Returns the value/values deleted. 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. {{version.project.key}} - Returns the project key of the project the version belongs to. Do more to earn more! twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. Note that environment contains additional nested smart values. Issues in Jira rarely exist in isolation. Which Jira-server version supports the use of smart value: "{{#if }} text {{/}}, or is this a Jira-cloud only functionality ? I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). If a condition fails, the rule will stop running and no actions following the condition will be performed. Learn more about automation triggers. You could then use this to count the number of issues returned. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. Join now to unlock these features and more. Examples of using smart values with lists. {{commit.message}} returns the commit message, e.g. Learn more about date smart values. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. Here is an example automation rule which can be used as a templated rule for creating a Release Center Epic from any (or selected) Jira Software project versions automatically: Rule step. This was something we have added since the split and I suspect that the server team has not caught up. Added by: Send web request with "Wait for response" checkedOn successful request, you will be able access webhook response data using the following smart values: Multiple responses can be access via the following fields: Added by: Worklogged TriggerThe worklog entry that has just been logged against an issue. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. This can be obtained by sending a webhook to a webhook test site (like https://requestbin.com) or by intercepting the message by enabling Jira's HTTP access logs and HTTP dump from the System > Logging and Profilingscreen and then checking the request data. For example, if a rule is created that will comment on an issue when executed, the rule actor must have the Add comment permission, otherwise the rule will result in an error. The issue is not so much with the smart values itself, but with the {{#if }} statement. Or you could count how many issues have the same label, same fixVersion, etc. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. {{branch.repository}}). I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. In the project menu, click on Project Settings. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. The URL to access the issue. You can find some automation templates to help you get started within the product library. {{issue.comments.last.body}} - Returns the body of the last comment. Learn more about services in Jira Service Management, Learn more about configuring time tracking. {{rule.actor}} - Accesses the rule actor user. Accesses any issue property. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. Fix versions of an issue as a list. For example, you might count how many issues have a priority of 'highest' and then send an alert. Smart values allow you to access and manipulate a wide range of issue data within your site. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. Learn more about list smart values. https://bitbucket.org/account/repo/TEST-123-some-feature, {{pullRequest.destinationBranch.repository}}, https://bitbucket.org/{7faf7dee-a29b-4faa-bbc2-d7128a6d3278}/{315a3ecb-1f18-4953-98ae-5890f93073b5}/addon/pipelines/home#!/results/7, [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work], https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. What goes around comes around! {{commit.hash}} returns the SHA1 hash of the commit, e.g.4877576951f3eda43625d3345058e702dad3df0d. {{pullRequest.destinationBranch}} returns information related to the destination branch of the pull request. Because this smart value deals with multiple items (i.e: issues can have many watchers), it can be used with the#symbol to apply the rule to each individual component. Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. A build represents the process in which files are converted into their final consumable form. {{createdBranches.product}} - returns the products that the branches were created in. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. [Custom Field].name}} - Returns the visible label displayed on the left of the field. 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. You can access all fields of the Epic. Properties are frequently used by add-ons and integrations to store values, e.g. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. all fields available to{{issue}}are available here as well. The following example prints all the issue keys returned from the JQL search, in bullet point form. Whenever you want to edit a field in Jira, use the Edit issue action. Each field is a list of changes. {{createdBranches.name}} - returns the names of the branches, {{createdBranches.url}} - returns the URLs of the branches. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. Affects version of an issue as a list. For example, checking that all sub-tasks of a parent issue are resolved. As a result of this design, the automation got initiated while triggered by a transition, however the data needed for the automation could not be yet updated. If this issue is a sub-task, then parent refers to the parent issue. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. If multiple values are changed, use # to iterate over these. For example, the smart value{{now.plusDays(5)}} references the current time and adds 5 days to it, while {{issue.summary}} will print off the summary of the issue. {{version.startDate}} - Returns the version's start date. These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. {{issue.affectedServices.changeApprovers}} - Returns the account ID of all change approvers of the issue's services. This applies to the legacy Insight app. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. What goes around comes around! Triggers can be set to run manually, based on a condition you set or scheduled. In this case, we want to choose the Field value changed trigger. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. 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. For more information on this, see Configuring a webhook later on this page. Find issues that have the same custom field date as trigger issue. Go to Jira administration console > System > Webhooks (in the Advanced section). {{version.description}} - Returns the version's description. Approval required: accesses information when an issue that requires approval is created or updated, or when new approvers are added to an issue. A branch represents an independent line of development. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. {{issue.parent.key}} - Returns the issue key of the subtask's parent issue. :{{issue.properties.some.value}}. All of the issues found by the trigger are then treated as a single bundle of issues. You must be a registered user to add a comment. Learn more about user smart values. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. Learn more about using smart values with sections and lists. See all smart values used to insert conditional logic such as if/equals/and statements into comments and other text fields. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Examples of how you can use smart values to manipulate and format dates in your Jira automation rules. Your image appears to show too many curly-brackets around the value. Similar to{{issue. You can also use this withlists. Here, we choose the Issue fields' condition and clarify that the issue type we are looking out for is a sub-task. Any idea if this will be added, and if so when? If you've already registered, sign in. Otherwise, register and sign in. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. E.g. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. Access information related to all branches created in the rule, as a list. Keep earning points to reach the top of the leaderboard. {{commit.repository.name}} returns the name of the repository, e.g. Used to access the values in an issue'sFix Versionsfield. Added by: Jira Triggers that edit an issue, All the fields that were changed. Available anywhere smart values are supported, to access the value of a field that has changed. Through the dot notation you can access fields like issue type, status and custom fields (details on how you can use these to interact with Jira's REST api arehere). I'll mention the docs discrepancies to the person that maintains our documentation. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate.
