Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. 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. However, you can now change the rule actor for your automation rules. Learn more about using smart values with sections and lists. 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. For example, you might count how many issues have a priority of 'highest' and then send an alert. this is only available for some triggers. 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. {{rule.name}} - Returns the name of the rule that is currently running. {{createdBranch.repository.url}} - returns the repositorys URL. These smart values can only be accessed through other root keys (e.g. Understand the general concepts and best practices of automation in Atlassian Cloud products. Refers to the original issue when you branch the chain. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. Wonderful :). Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. {{versions.name}}- Returns the name of the affects version. Instead using Re-fetch for Cloud slows the rule for about 1 second (or more). If this issue is in an Epic, then epic refers to the Epic issue. {{issue.InsightField}} - Returns the issue summary and issue key, {{issue.InsightField.key}} - Returns the issue key, {{issue.InsightField.summary}} - Returns the issue summary. I am glad to learn that helped you. After testing, disable both the HTTP dump and access logs to avoid performance issues. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. Join the Kudos program to earn points and save your progress. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. Added by: Sprint created, started or completed triggers. [Custom Field].defaultValue}} - Returns the value displayed on first view of the field. And we have lots more automation templates and guides for you to use and learn from in the automation template library. :{{issue.properties.some.value}}. The example below lists each person watching the issue - both their display name and their email address - in bulletpointform. Only one word but It changes the whole picture. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. 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). Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. You can check this by navigating to the "Custom fields" page in the. {{comment.body}} - Returns the body of the comment that triggered the rule. : To do,In progress, orDone). Can be combined with other date smart values. Possible states include pending, in_progress, successful, failed, cancelled, or unknown. You can access an insight field's full name, key, or summary through the following smart values: You can access a Tempo Account field's properties through the following smart values: To test what your smart value returns, use the, The active issue. For example, {{attachment.first.size}} will return the file size of the first attachment. All properties available to{{issue}}are also available on this smart value. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. You're on your way to the next level! {{deletedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to deletion of a value. Join the Kudos program to earn points and save your progress. These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. Keep earning points to reach the top of the leaderboard. Accesses time tracking estimates. Available only for the pull request created trigger. Send a daily Slack message with a list of issues still open in the Sprint. {{issue.latest.description}} - Returns the status's description. Acording with the documentation, Automation JQL condition suport smart values. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). Field value changed Available in Server Lite: No {{issue.epic. 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. Are you looking for server documentation? {{issue.timetracking.remainingestimate}} - Returns the value in the Time remaining field. If multiple values are changed (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. OMGYou're right. all fields available to{{issue}}are available here as well. A list of issues that have been created in the rule. I found both of these smart values seemed to work: If neither of these work for you, there are a few other options in those linked questions you can try :), {{sprint.name}} returns only the sprint that started and which triggered this automation event. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. {fieldChange.toString}}- Returns the new value as displayed. When there are multiple fields that have changed, {{fieldChange}}only contains the first changed value. Accesses the previous issue created in the rule. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. Returns a list of issues from a JQL search caused bythe Lookup issues action. Check out how we use smart values in our Jira automation template library. Returns the value of the Jira Service Managements rate custom field. Learn more about using smart values with sections and lists. If more than one flag has been created throughout the rule, {{flag}} will return the most recently-created flag. Note that environment contains additional nested smart values. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. The active issue. A pull request represents proposed changes before they are integrated into an official project. In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. {{attachment.author}}: Returnsthe user who added the attachment. Used to access information about an issue's epic. What goes around comes around! In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- We do not currently support accessing fields within insight objects. Learn more about date and time smart values. Now whenever this field changes in Jira, this automation rule kicks in. {{deployment.state}} returns the state of the deployment. {{attachment.author.emailAddress}}: Returnsthe email address associated with the user name. {{createdBranch.name}} - returns the name of the branch, {{createdBranch.url}} - returns the URL of the branch. Available anywhere smart values are supported, to access the value of a field that has changed. A build represents the process in which files are converted into their final consumable form. {{version.description}} - Returns the version's description. Accesses information fromJira Service Managementrequests. For Jira Service Management requests only. action: log to the audit file this value. Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms. If I use a smart value of type: {{sprint.name}} the field returns me all the sprints that exist in the "sprint" field, including those that are already closed. 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. [Custom Field].name}} - Returns the visible label displayed on the left of the field. {{issue. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. for a select field. https://bitbucket.org/account/repo/TEST-123-some-feature. {{pullRequest.sourceBranch}} returns the name of the source branch, e.g. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. Also provides the customer portal URL for Jira Service Management issues. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). For example, you might count how many issues have a priority of 'highest' and then send an alert. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. Learn more about list smart values. 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. All of the issues found by the trigger are then treated as a single bundle of issues. Jira smart values in automation rules. This value supportsDate and Time functions. Join the Kudos program to earn points and save your progress. You can access all fields of the parent. {{issue.description}} - Returns the content in the issue'sDescriptionfield. Challenges come and go, but your rewards stay with you. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. 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. For example, you can use the following smart values to send a Slack message that includes the issue key and issue summary: { {issue.key}} { {issue.summary}} Check out how we use smart values in our Jira automation template library. 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. {{commit.message}} returns the commit message, e.g. Learn more about using smart values with sections and lists. In the project menu, click on Project Settings. FR Jira Dev Aug 05, 2021 I currently have an Automation workflow that creates multiple tasks and subtasks. {{issue.comments.first.body}} - Returns the body of the first comment. Used with: the Send web request action (Wait for response enabled). Because this smart value deals with multiple items (i.e: issues can have many Affects versions), it can be used with the#symbol to apply the rule to each individual component. Please share more details and screenshots in order to be able to help you. These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. {{assignee.displayName}} - Returns the assignee, {{reporter.displayName}} - Returns the reporter, {{issueType.name}} - Returns the issue type, {{resolution}} - Returns the resolution status, {{created}} - Returns the date the issue was created, {{updated}} - Returns the date the issue was updated, {{Story Points}} - Returns the story points for the issue (company-managed Jira Software), {{Story point estimate}} - Returns the story points for the issue (team-managed Jira Software). Exclusive to the Approval required trigger: {{approval.initiator}} - Returns account id of initiator of request. I suspect not. In this way, approval returns two different values depending on the trigger being Approval required or Approval completed - https://support . Seeaccesing multi-value fields, Added by: This is added any time an issue is added. Join now to unlock these features and more. Is the IF statement available for Server version? 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. 4877576. {{versions.releaseDate}}- Returns the affects version's release date. See all smart values that take issue fields and convert them into JSON format. 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, Version created, Version updated, and Version released triggers. {{version.project.key}} - Returns the project key of the project the version belongs to. {{sprint.completeDate}} -Returns date the sprint was marked as complete. Note that repository contains additional nested smart values. For example, when an issue is transitioned you can see what status the issue transitioned from. Awesome! Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. If this issue is in an Epic, then epic refers to the Epic issue. text {{/}}, or is this a Jira-cloud only functionality ? {{versions.archived}}- Returnstrueif the affects version is archived, andfalseif not. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. Join now to unlock these features and more. These smart values can only be accessed through other root keys (e.g{{deployment.environment}}). This smart value requires an expensive reload of issue data and should only be used in situations where subsequent actions need to have visibility of the latest state of an issue, e.g. Looking forward to see it implemented soon! When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. 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) The rule triggers on 'Issue created' and is followed by the 'Send web request' component. If a rule is inactive, it will not execute until it is enabled. When we use this trigger, we can use the {{webhookData}} smart value to represent the POST payload - we'll focus on this here. Triggers can be set to run manually, based on a condition you set or scheduled. This smart value only works for issues that have been added to an epic. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. - Any ideas on this one? See all smart values that are used to insert and format numerical values using math expressions. {{build.name}} returns the name of the build, e.g. {{versions.description}}- Returns the description of the affects version. 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). Learn how to use these to interact with Jiras REST API. {{fieldChange}}only contains the first changed value. {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. I created an automation that created a value in a short text field. {{branch.repository}} returns information related to the repository the branch belongs to. {{addedfieldChange.values}} - Returns the new value/values added. {{issue.parent.epic.summary}} - Returns the summary of the parent issue's epic. {{changelog.summary}} - Changelog information for theSummaryfield. [property]}} For example, you might count how many issues have a priority of 'highest' and then send an alert. Automation is a great way to reduce the manual work of keeping story points up to date. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. Navigate to your project in Jira. Learn more about user smart values. 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. Your image appears to show too many curly-brackets around the value. Summary Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. Keep earning points to reach the top of the leaderboard. Or .displayName if accountId doe not work as hoped. Share the love by gifting kudos to your peers. E.g. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. 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. The rule is running too quickly after the issue is created. Set the Equals condition to true. Your smart value must identify a specific attachment for this to work. See all smart values that can manipulate the values of items in a list. This example returns an issue's previous type, after it has been changed. Do more to earn more! These can be combined with other user smart values. Connect your source code management, build or deployment tool to use these smart values. {{environment.name}} returns the use-provided name for the environment, e.g. They enable customizing automation actions to be useful for your team and your customers. They kick off the execution of your rules. 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. 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. Step 3: Set up the condition like this: Change the field's value to Issue Type. Learn more about services in Jira Service Management, Learn more about configuring time tracking. Refers to the original issue when you branch the chain. Learn more about list smart values. Now, I want to run automation even without a sprint trigger (scheduled trigger). Fix versions of an issue as a list. 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! What are conditions? A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. Keep earning points to reach the top of the leaderboard. build#123, {{build.url}} returns the absolute URL of the build, e.g. These smart values are only available for the Build successful, Build failed and Build status changed development triggers. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. Thisshould not be usedsince it requires an expensive reload of issue data.