Hi John, thanks a lot for your quick response. We will ensure the story points of the parent and sub-task always remain in sync. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. What goes around comes around! Approval completed: accesses information for an approval when an approval step on an issue is accepted or declined. Used to access the values in an issue'sFix Versionsfield. Set the Equals condition to true. Automation allows you to focus on the work that matters, removing the need to perform manual, repetitive tasks by allowing your teams to automate their tasks, processes, and workflows. Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. On successful request, you will be able access webhook response data using the following smart values: The worklog entry that has just been logged against an issue. Your thorough reply here helped me in a completely different use case. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. Whenever you want to edit a field in Jira, use the Edit issue action. These smart values are only available for the Pull request created, Pull request declined and Pull request mergedtriggers. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. {{commit.message}} returns the commit message, e.g. {{approval.decision}} - Returns the final decision of the approval. Used with: the Create feature flag in LaunchDarkly action. Available anywhere smart values are supported, to access the value of a field that has changed. 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. This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. First, you need a sample from the webhook payload data. The following example prints all the issue keys returned from the JQL search, in bullet point form. Can be combined with other date smart values. {{issue.Request Type.requestType.name}} - Returns the customer request type. Can be combined with other date and time smart values. {{flags.name}} returns the name of the feature flag. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. {{changelog.status}} - Changelog information for theStatus field. - Any ideas on this one? 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. Accesses the values in an issue'sAffected services field. Returns information related to all feature flags created in throughout the rule or branch, as a list. But it looks like functionality for the Jira cloud version. Is there a smart value that returns me only the name of the trigger sprint or at least only the name of the open sprint? Learn about the concepts and procedures related to automation in Jira Cloud, Smart values allow you to access issue data within Jira. {{rule.actor}} - Accesses the rule actor user. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. 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. {{deletedFieldChanged.values}} - Returns the value/values deleted. This value won't work for any other trigger, even if a comment was added as a result (e.g. global admin section. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. This example shows the previous status for issues that are transitioned. A list of issues that have been created in the rule. The issue smart values are used to access information related to the rules active issue, which is the issue the rule is currently acting on. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. Here you can access any issue property. To get a property in it, we should use{{webhookData.someValue.childValue}}. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. Accesses information fromJira Service Managementrequests. Properties are frequently used by add-ons and integrations to store values, e.g. Jira automation - Data Center and Server (Latest), Examples of using smart values with dates, Examples of using smart values with lists, Examples of using math expression smart values, Examples of using smart values with text strings. Awesome! For example, if a rule uses the Create feature flag in LaunchDarkly action multiple times, {{flags} will return the information for all feature flags created, as a list. 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. Some issue properties are more complex, and theyve been described in their own sections on this page. They are using the curly-brace syntax like { {someSmartValue}} . Seeaccesing multi-value fields, Added by: This is added any time an issue is added. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Smart values are one of the most potent ways to do so. {{sprint.startDate}} - Returns the start date of the sprint. {{branch.repository.name}} returns the name of the repository. You could then use this to count the number of issues returned. You can access the current watchers of an issue. [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. {{addedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to addition of a value. Examples of how you can use smart values to set the text value of an issues field, such as Summary or Description. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. {{attachment.author.timeZone}}: Returns the timezone the user is registered being in; this doesn't change dynamically based upon where the user logs in from, it is the timeZone registered in their user account. It resets every quarter so you always have a chance! Do you have any idea how I find active sprint smart value? There should be a locked field named either "Request Type" or "Customer Request Type" there. General triggers These triggers can be used across all Jira products. https://bitbucket.org/account/repo/TEST-123-some-feature. {{issue.fixVersions.name}} - Returns the name of the fix version. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{branch.repository}}). Join the Kudos program to earn points and save your progress. @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 ! {{createdBranch.product}} - returns the product that the branch was created in (for example, Bitbucket). After testing, disable both the HTTP dump and access logs to avoid performance issues. https://bitbucket.org/{7faf7dee-a29b-4faa-bbc2-d7128a6d3278}/{315a3ecb-1f18-4953-98ae-5890f93073b5}/addon/pipelines/home#!/results/7, {{build.state}} returns the state of the build. The trigger for automation is starting a new sprint (trigger = start sprint). Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- Smart values allow you to access and manipulate a wide range of issue data within your site. Can be combined with other date and time smart values. {{environment.name}} returns the use-provided name for the environment, e.g. Affects version of an issue as a list. Learn more about date smart values. You can also use this withlists. A selection of smart values make Jira issue details readily available for Automation for Jira rules. We do not currently support accessing fields within insight objects. {{changelog.issuetype}} - Changelog information for theIssue type field. Smart values in Jira automation. {{issue.comments.reverse.body}} - Returns the issue's comments, in reverse order. Used with: any triggers that edit an issue. There is a feature request for it though - check outAUT-648. And the rule itself? issue The active issue. Available only for the pull request created trigger. You could then use this to count the number of issues returned. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). These smart values are only available for the Commit created development trigger. 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. TEST-123-some-feature, {{branch.url}} returns the URL of the branch, e.g. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. [property]}} See all smart values that access and manipulate Jira issue data such as sprint, parent, or version. You can specify a default value to prevent this. You're on your way to the next level! {{issue.affectedServices.tier}} - Returns the tiers of the issue's Affected services. {{attachment.author.emailAddress}}: Returnsthe email address associated with the user name. You're on your way to the next level! If this issue is a sub-task, then parent refers to the parent issue. For example,jira:issue_updated :issue_commented. When an epic is marked as done move all of its stories to done also. The spacing format is mentioned in the following article: New automation smart values in Jira Cloud, https://jira.atlassian.com/browse/JIRAAUTOSERVER-212, Smart-value-in-published-article-doesn-t-work. 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. {{attachment.filename}}: Returns the filename of the attachment. Understand the general concepts and best practices of automation in Atlassian Cloud products. {{issue.comments.first.body}} - Returns the body of the first comment. Select Automations - Create Rule. With our simple no-code rule builder, you can create automation rules to take care of everything from the most simple repetitive tasks to the most complex scenarios - all in a few clicks. Use{{fieldChange.fromString}}and{{fieldChange.toString}}to access display values and{{fieldChange.from}}and{{fieldChange.to}}to access raw values (for a select field for example). You can also use the quick search (keyboard shortcut is . Learn more about automation triggers. Examples of using smart values with dates. Use an IDE like Visual Studio Code to find the path. It is better to use this than name as it cannot be changed. For example, you might count how many issues have a priority of 'highest' and then send an alert. Note that repository contains additional nested smart values. Accesses a Tempo Account field's properties. What third-party applications can I integrate with? Note that repository contains additional nested smart values. Learn more about using smart values with sections and lists. Added by: Sprint created, started or completed triggers. {{issue.updated}} - Returns the date the issue was updated. 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 here) twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. {{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. A commit represents an individual change to a file (or set of files). Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Step 2: Save the Issue generated trigger. 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. Accesses the details of a subtask's parent issue. Or you could count how many issues have the same label, same fixVersion, etc. 4877576. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. In my use case I am receiving data from an API interface and the problem is that my automation is executed based on the transition and later there are a few branches, where one of them is selected based on some value in a custom field. These can be combined with other date and time smart values. There are many ways you can edit a field. The type of event that triggered the rule. {{issue. {{sprint.isClosed}} -Returnstrueif the sprint has closed, andfalseif not. Examples of using smart values with text strings. We do not currently support accessing fields within insight objects. In this component, we use the following settings:The email address of the reporter is captured in the smart value {{reporter.emailAddress}}, but we need to use it in a URL and therefore will use the smart value {{reporter.emailAddress.urlEncode . {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. Learn more about date smart values. And we have lots more automation templates and guides for you to use and learn from in the automation template library. {{version.id}} - Returns the version's ID. Returns the issue's comments. Learn more about using smart values with sections and lists. If multiple values are changed, use # to iterate over these. {{sprint.goal}} - Returns the sprint goal. Is there a way to similar functionality in Jira-Server? my-awesome-repository. The trigger for automation is starting a new sprint (trigger = start sprint).