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 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. Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. 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. A build represents the process in which files are converted into their final consumable form. . Refers to the original issue that triggered the rule; used when you branch the chain. You can also use the quick search (keyboard shortcut is . {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. What goes around comes around! To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. There are many ways you can edit a field. [Custom Field].name}} - Returns the visible label displayed on the left of the field. Learn more about automation triggers. You could then use this to count the number of issues returned. All of the issues found by the trigger are then treated as a single bundle of issues. 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. I created an automation that created a value in a short text field. Can be combined with other user smart values. {fieldChange.fromString}} - Returns the previous value as displayed. Go to Jira administration console > System > Webhooks (in the Advanced section). Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . {{issue.affectedServices.tier}} - Returns the tiers of the issue's Affected services. {{pullRequest.destinationBranch.repository}} returns information related to the destination branchs repository. {{sprint.endDate}} -Returns the end date of the sprint. Smart values are variables that you can use in automation action configuration parameters. Used by triggers that involve adding a comment, such as Issue commented, Issue transitioned, or Issue updated. {{createdBranch.product}} - returns the product that the branch was created in (for example, Bitbucket). {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. Do you have any idea how I find active sprint smart value? {{branch.name}} returns the name of the branch, e.g. Triggers, conditions, and actions are the building blocks of automation. Or you could count how many issues have the same label, same fixVersion, etc. {{issue.duedate}} - Returns theissue's due date. Triggers: Triggers wait for defined events to take place in your Jira instance and will then execute the automation rule. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. If you've already registered, sign in. Learn how to use these to interact with Jiras REST API. {{comment.properties. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. {{createdBranch.name}} - returns the name of the branch, {{createdBranch.url}} - returns the URL of the branch. {{pullRequest.destinationBranch}} returns the name of the destination branch, e.g.master, {{pullRequest.destinationBranch.url}} returns the URL of the destination branch, e.g. E.g. 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. See all smart values that can manipulate the values of items in a list. Learn about the concepts and procedures related to automation in Jira Cloud. These smart values are only available for the Pull request created, Pull request declined and Pull request mergedtriggers. {{branch.repository}}). Get answers to your question from experts in the community, Automation JQL condition: using smart values. Get answers to your question from experts in the community, Smart value of trigger issue in automation. Used with the Version created, Version updated, and Version released triggers. If more than one flag has been created throughout the rule, {{flag}} will return the most recently-created flag. {{environment.name}} returns the use-provided name for the environment, e.g. {{issue.description}} - Returns the content in the issue'sDescriptionfield. Refers to the original issue when you branch the chain. Would be good and useful functionality to have. We do not currently support accessing fields within insight objects. {{issue. They often contain sub-tasks, are stories that are part of a larger epic, or are simply linked to other issues using certain relationships. Refers to the original issue when you branch the chain. You must be a registered user to add a comment. role. To get a property in it, we should use{{webhookData.someValue.childValue}}. Can be combined with other user-related smart values. A list of issues that have been created in the rule. Every rule starts with a trigger. You must be a registered user to add a comment. 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. Keep earning points to reach the top of the leaderboard. What that error tells me one of three things is happening: Let's try this: immediately after your trigger, add two things: a) If the rule works after adding the re-fetch, the cause was #1, b) If the audit log does not show your date, it is either #2 or #3. These smart values are only available for the Build successful, Build failed and Build status changed development triggers. {{fieldChange.from}}- Returns the previous raw value, e.g. On successful request, you will be able access webhook response data using the available smart values. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. I am glad to learn that helped you. {{sprint.isStarted}} - Returnstrue if the sprint has started, andfalse if not. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. 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. What are conditions? Challenges come and go, but your rewards stay with you. 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. You can check this by navigating to the "Custom fields" page in theglobal admin section. It is better to use this than name as it cannot be changed. 200, {{webhookResponse.headers}} - headers that can be accessed with dot nation, {{webhookResponse.body}} - body that can be accessed with dot nation, {{webhookResponses}} - list of responses made when list operations. 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). The information that you can access on the issue are described in the Available properties section below. my-awesome-repository. I'll ask one of their team to update you here. To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms. {{issue.reporter.displayName}} - Returns the issue's reporter. {{attachment. Examples of using smart values with dates. Only one word but It changes the whole picture. A condition refines the rule so it wont act too broadly. It may contain, for example, branches and tags names.This value is optional and may be an empty list. Learn more about list smart values. Understand the general concepts and best practices of automation in Atlassian Cloud products. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. You're on your way to the next level! 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. {{issue. [Custom Field].defaultValue}} - Returns the value displayed on first view of the field. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. And we have lots more automation templates and guides for you to use and learn from in the automation template library. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. Examples of how you can use smart values to set the text value of an issues field, such as Summary or Description. my-custom-prod-env, {{environment.type}} returns the environment type. A commit represents an individual change to a file (or set of files). Note that repository contains additional nested smart values. These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. {{version.name}} - Returns the version's name. For smart values related to the Insight feature in Jira Service Management, see Jira smart values - Assets. Learn more about configuring time tracking. Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. {{pullRequest.createdDate}} returns the time (UTC) when the pull request was created, e.g. General triggers These triggers can be used across all Jira products. For more information on when issues is available, seeRun a rule against issues in bulk. 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) {{issue.url}} - Returns the URL of the issue. Available anywhere smart values are supported, to access the value of a field that has changed. 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. Wonderful :). {{issue.epic. {{attachment.filename}}: Returns the filename of the attachment. Accesses the value in the issue'sAffects versions field. 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. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. {{versions.archived}}- Returnstrueif the affects version is archived, andfalseif not. Possible states include pending, in_progress, successful, failed, cancelled, or unknown. For example, PROJ-123. 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. {{build.name}} returns the name of the build, e.g. When there are multiple fields that have changed, {{fieldChange}}only contains the first changed value. This example shows the previous status for issues that are transitioned. {{issue.components.name}}- Returns the values in the issue'sComponentfield. https://bitbucket.org/account/repo. Thisshould not be usedsince it requires an expensive reload of issue data. Exclusive to the Approval required trigger: {{approval.initiator}} - Returns account id of initiator of request. 2020-07-20T07:00:00.0+0000. These smart values are only available for the Commit created development trigger. Automation is currently available in Jira Software Cloud and Confluence Cloud. Accesses the values in an issue'sAffected services field. Because this smart value deals with multiple items (i.e: issues usually have many comments), it can be used with the # symbol to apply the rule to each individual comment. 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. Join now to unlock these features and more. See all smart values related to Assets in Jira Service Management Cloud. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. You can view the audit log of an individual rule, project-wide or at a global level. Step 3: Set up the condition like this: Change the field's value to Issue Type. Here, we choose the Issue fields' condition and clarify that the issue type we are looking out for is a sub-task. First, you need a sample from the webhook payload data. Step 4: Add 'Edit Issue' action . Are you looking for server documentation? This means that when using automation, actions often need to apply, not only to the source issue that triggered the rule, but also to any issues that are related to the source issue. {{deployment.environment}} returns information related to the deployment environment. 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. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- {{approval.addedApprovers}} - Returns the set of approvers added to issue. {{issue.watchers.emailAddress}} - Returns the watcher's email address. . Can be combined with other date and time smart values. {{issue.created}} - Returns the issue's creation date. {{changelog.status}} - Changelog information for theStatus field. Set the Equals condition to true. We use the following smart-value to sum up story points from all sub-tasks: {{issue.subtasks.Story Points.sum}}. These smart values can only be accessed through other root keys (e.g. Join the Kudos program to earn points and save your progress. Your image appears to show too many curly-brackets around the value. {{flags.name}} returns the name of the feature flag. {{createdBranches.name}} - returns the names of the branches, {{createdBranches.url}} - returns the URLs of the branches. They kick off the execution of your rules. What I didn't notice, is that I entered the value: {{issue.sprint.name}}. If a rule is inactive, it will not execute until it is enabled. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. However, you can now change the rule actor for your automation rules. {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. There are many ways you can edit a field. And the rule itself? Some issue properties are more complex, and theyve been described in their own sections on this page. {{pullRequest.title}} returns the title of the pull request, e.g. global admin section. https://bitbucket.org/account/repo/TEST-123-some-feature. Learn more about list smart values. Added by: Sprint created, started or completed triggers. {{issue.comments.size}} - Returns the number of comments on the issue. Do more to earn more! When an issue is raised without an assignee, auto-assign to whoever created it. I suspect not. If a condition fails, the rule will stop running and no actions following the condition will be performed. When we use this trigger, we can use the {{webhookData}} smart value to represent the POST payload - we'll focus on this here.
