Affects version of an issue as a list. {{commit.repository.url}} returns the repositorys URL. A build represents the process in which files are converted into their final consumable form. action: Re-fetch issue (This will slow down the rule by reloading the newly created issue, as all of the data may not be ready when the rule runs.). {{build.refs}} returns the refs of the build, e.g. https://bitbucket.org/account/repo/TEST-123-some-feature. There is a feature request for it though - check outAUT-648. {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. {{issue.created}} - Returns the issue's creation date. You must be a registered user to add a comment. Learn more about using smart values with sections and lists. The URL to access the issue. Or .displayName if accountId doe not work as hoped. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. text {{/}}, or is this a Jira-cloud only functionality ? Summary Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. This applies to the legacy Insight app. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. {{approval.addedApprovers}} - Returns the set of approvers added to issue. Can be combined with other user-related smart values. There should be a locked field named either "Request Type" or "Customer Request Type" there. {{issue.Request Type.requestType.name}} - Returns the customer request type. Learn more about automation triggers. You can check this by navigating to the "Custom fields" page in theglobal admin section. For more information on when issues is available, seeRun a rule against issues in bulk. {{version.id}} - Returns the version's ID. E.g. {{attachment.created}}: Returnsthe date and time the attachment was added to the issue. {{versions.name}}- Returns the name of the affects version. Or you could count how many issues have the same label, same fixVersion, etc. It is better to use this than name as it cannot be changed. You were right, the rule was running too quickly, so the field was empty.I modify de trigger to give it time, and got the result expected. Triggers can be set to run manually, based on a condition you set or scheduled. Accesses information related to a file attachment on an issue. I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). Used with: the Send web request action (Wait for response enabled). {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. {{commit.message}} returns the commit message, e.g. 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. awesome commit handles everything, {{commit.url}} returns the absolute URL of the commit, e.g. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. {{issue.watchers.displayName}} - Returns the watcher's display name. All of the issues found by the trigger are then treated as a single bundle of issues. For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. If you've already registered, sign in. Please raise suggestion ticket in our public tracker, https://jira.atlassian.com/projects/JIRAAUTOSERVER. Used with the Version created, Version updated, and Version released triggers. Added by: Sprint created, started or completed triggers. {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value. {{issue.timetracking.remainingestimate}} - Returns the value in the Time remaining field. Added by: Jira Triggers that edit an issue, All the fields that were changed. The example below lists each person watching the issue - both their display name and their email address - in bulletpointform. Some issue properties are more complex, and theyve been described in their own sections on this page. Learn more about date smart values. {{issue.epic.key}} - Returns the epic's key, e.g. However, you can now change the rule actor for your automation rules. If a condition fails, the rule will stop running and no actions following the condition will be performed. Again say it aloud: Whenever the field value changes for story points AND it is a sub-taskTHEN for the parent of the sub-task. 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. The trigger for automation is starting a new sprint (trigger = start sprint). {{issue.fixVersions.description}} - Returns the description of the fix version. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. {{deletedFieldChanged.values}} - Returns the value/values deleted. Thisshould not be usedsince it requires an expensive reload of issue data. Accesses a Tempo Account field's properties. With the 're-fetch issue data' action (which I seldom use), I noticed that this can put the automation execution on-hold for the whole 5 seconds! Please try just two around each side: Of note: what is the type of your field? This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. Learn more about date and time smart values. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. {{commit.hash}} returns the SHA1 hash of the commit, e.g.4877576951f3eda43625d3345058e702dad3df0d. In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. {{sprint.startDate}} - Returns the start date of the sprint. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. {{issue.affectedServices.changeApprovers}} - Returns the account ID of all change approvers of the issue's services. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. Accesses the previous issue created in the rule. Challenges come and go, but your rewards stay with you. {{deployment.state}} returns the state of the deployment. {{versions.description}}- Returns the description of the affects version. You can access all fields of the Epic. : To do,In progress, orDone). 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. What I didn't notice, is that I entered the value: {{issue.sprint.name}}. https://bitbucket.org/account/repo/TEST-123-some-feature. 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). {{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. {{comment.body}} - Returns the body of the comment that triggered the rule. The smartvalue{{webhookData}}gets the root of the JSON payload. What goes around comes around! {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. Field value changed Available in Server Lite: No The Atlassian Community can help you and your team get more value out of Atlassian products and practices. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. https://bitbucket.org/account/repo/TEST-123-some-feature. All of the issues found by the trigger are then treated as a single bundle of issues. What third-party applications can I integrate with? This example shows the previous status for issues that are transitioned. Used with: the Clone issue, Create issue, and Create sub-tasks actions. You can check this by navigating to the "Custom fields" page in the. {{branch.name}} returns the name of the branch, e.g. 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. https://bitbucket.org/commit/121212, {{commit.isMergeCommit}} returns True if commit is a merge commit, {{commit.timestamp}} returns the timestamp (UTC) the commit was created. A pull request represents proposed changes before they are integrated into an official project. The trigger for automation is starting a new sprint (trigger = start sprint). {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. Learn more about using smart values with sections and lists. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Note that repository contains additional nested smart values. The active issue. 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. Is the IF statement available for Server version? Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. Do more to earn more! They allow you to automate tasks and make changes within your site. If this issue is in an Epic, then epic refers to the Epic issue. 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. Access information related to the last branch that was created. Added by: Jira Triggers that edit an issue, All the fields that were changed. {{createdBranches.product}} - returns the products that the branches were created in. 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. Check out how we use smart values in our Jira automation template library. You can also use this withlists. A representation of a release/version in Jira. Access information related to all branches created in the rule, as a list. Smart values allow you to access and manipulate a wide range of issue data within your site. "sd.public.comment".internal}} -. Any idea if this will be added, and if so when? The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. {{issue. If this issue is in an Epic, then epic refers to the Epic issue. {{issue.affectedServices.changeApprovers}}, {{issue.affectedServices.changeApprovers.displayName}}, {{issue.affectedServices.dependentServices}}, {{issue.affectedServices.dependentServices.tier}}, {{issue.Request Type.currentStatus.status}}, {{comment.properties. 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. {{fieldChange}}only contains the first changed value. Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. {{rule.actor}} - Accesses the rule actor user. When there are multiple fields that have changed, {{fieldChange}}only contains the first changed value. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. {{issue.comments.reverse.body}} - Returns the issue's comments, in reverse order. {{build.name}} returns the name of the build, e.g. Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. [property]}}, you can also access custom field information on your issues. You can also use this with, . {{comment.visibility.type}} - Returns the comment restriction type if any, e.g. See all smart values related to user fields, such as Reporter or Assignee. {{attachment.filename}}: Returns the filename of the attachment. Understand the general concepts and best practices of automation in Atlassian Cloud products. Connect thousands of apps for all your Atlassian products, Run a world-class agile software organization from discovery to delivery and operations, Enable dev, IT ops, and business teams to deliver great service at high velocity, Empower autonomous teams without losing organizational alignment, Great for startups, from incubator to IPO, Get the right tools for your growing business, Docs and resources to build Atlassian apps, Compliance, privacy, platform roadmap, and more, Stories on culture, tech, teams, and tips, Training and certifications for all skill levels, A forum for connecting, sharing, and learning. You can view the status of an automation rule to identify if the rule is currently active or not. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. This re-fetches the latest state of the issue from Jira. You can access the current watchers of an issue. When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. And the rule itself? {{changelog.status}} - Changelog information for theStatus field. this is only available for some triggers. Examples of using smart values with lists. Returns a list of issues from a JQL search caused bythe Lookup issues action. issue The active issue. They are using the curly-brace syntax like { {someSmartValue}} . 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.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. They are variables in the sense that their actual values will be calculated while the automation rule is being executed: You can use two types of smart values: 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) Seeaccesing multi-value fields, Added by: This is added any time an issue is added. 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. They allow you to access and manipulate almost any data in Jira. Returns the value of the Jira Service Managements rate custom field. Thanks for sharing the link back in this question, it might help others in future! Smart values are one of the most potent ways to do so. If this issue is a sub-task, then parent refers to the parent issue. 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 . {{branch.repository}} returns information related to the repository the branch belongs to. Which Jira-server version supports the use of smart value: "{{#if . }} {{issue. {{flag.name}} returns the name of the feature flag. this is only available for some triggers. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. Also provides the customer portal URL for Jira Service Management issues. Examples of using smart values with text strings. {{issue.Story Points}} - Returns the issue's story point estimate (company-managed Jira Software Cloud only). {{issue.components.name}}- Returns the values in the issue'sComponentfield. {{deletedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to deletion of a value. After testing, disable both the HTTP dump and access logs to avoid performance issues. You can set triggers to run on a schedule or as needed. This value won't work for any other trigger, even if a comment was added as a result (e.g. 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.Request Type.currentStatus.status}} - Returns the status of the current request. As ever, test this rule out in your own instance. 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). Affects version of an issue as a list. {{issue.updated}} - Returns the date the issue was updated. These smart values are only available for the Branch created development trigger. These smart values can only be accessed through other root keys (e.g. {{worklog.visibility}} -available when the worklog is restricted, {{worklog.visibility.type}} -available when the worklog is restricted, {{worklog.visibility.value}} -available when the worklog is restricted. These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. Connect your source code management, build or deployment tool to use these smart values. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. Triggers can be set to run manually, based on a condition you set or scheduled. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. 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. Learn more about list smart values. Possible states include pending, in_progress, successful, failed, cancelled, rolled_back, or unknown. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. That looks a little odd. If youre an Automation for Jira app customer on a server product, check out the Automation for Jira documentation for Jira Server. We will ensure the story points of the parent and sub-task always remain in sync. Join the Kudos program to earn points and save your progress. When an issue is raised without an assignee, auto-assign to whoever created it. You can also trigger rules to run from third party services like Bitbucket or GitHub. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. TEST-123-some-feature, {{branch.url}} returns the URL of the branch, e.g. {{pullRequest.sourceBranch}} returns information related to the source branch for the pull request. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. The rule is running too quickly after the issue is created. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. It resets every quarter so you always have a chance! Learn more about date and time smart values. All properties available to{{issue}}are also available on this smart value. This example returns the new value of an issue'sSummary field after it has been changed. Would be good and useful functionality to have. global admin section. Affects version of an issue as a list. Go to templates. Returns the value of the Jira Service Managements scale custom field. Can be combined with other date and time smart values. Get answers to your question from experts in the community, Automation JQL condition: using smart values. You can check this by navigating to the "Custom fields" page in the. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. {{version.releaseDate}} - Returns the version's release date. Do you have any idea how I find active sprint smart value? Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. Used to access the values in an issue'sFix Versionsfield. Awesome! Returns the value of the Jira Service Managements scale custom field. :{{issue.properties.some.value}}. Story points are integral for many agile teams. {{pullRequest.sourceBranch}} returns the name of the source branch, e.g. {{versions.archived}}- Returnstrueif the affects version is archived, andfalseif not. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. {{addedfieldChange.values}} - Returns the new value/values added. Step 2: Save the Issue generated trigger. And we have lots more automation templates and guides for you to use and learn from in the automation template library.