It resets every quarter so you always have a chance! When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. 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. Challenges come and go, but your rewards stay with you. The option to created linked issues (and then pick the blocked option) exists, but only to pick the issue from the trigger value or the most recently created issue to create a link. {{createdBranches.product}} - returns the products that the branches were created in. 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) Automation rules are made up of three parts: triggers that kick off the rule, conditions that refine the rule, and actions that perform tasks in your site. Used with: the Create feature flag in LaunchDarkly action. 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. Jira smart values - issues | Automation for Jira Data Center and Server {{attachment.author.accountId}}: Returnsthe ID associated with the user name. 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. In this template, we show you how to sum up the story points of all sub-tasks then update the parent issue with this value. Advanced automation in Jira Service Desk - TMC Application Lifecycle The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. Triggers can be set to run on a schedule, and can be customized before being applied to a rule. If this issue is a sub-task, then parent refers to the parent issue. You could then use this to count the number of issues returned. You're on your way to the next level! {{issue.created}} - Returns the issue's creation date. {{approval}} - Returns the name of the approval. Learn more about date and time smart values. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. If more than one flag has been created throughout the rule, {{flag}} will return the most recently-created flag. Select the Issue fields condition from the New condition drop-down menu. Simply combine these components to create rules that can do anything from auto-closing old issues to notifying specific teams when a release has been shipped. Jira smart values in automation rules. You can specify a default value to prevent this. [Custom Field]}} - Returns the value in an epic's custom field. For example, when an issue is transitioned you can see what status the issue transitioned from. You can view the audit log of an individual rule, project-wide or at a global level. Accesses a Tempo Account field's properties. 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. my-custom-prod-env, {{environment.type}} returns the environment type. Used with: the Send web request action (Wait for response enabled). Jira Software Questions Smart value of trigger issue in automation Smart value of trigger issue in automation Eliyahu Klein Jan 09, 2023 Hi, I created an automation that created a value in a short text field. Added by: Sprint created, started or completed triggers. for a select field. Returns the value of the Jira Service Managements rate custom field. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. Jira smart values - issues | Cloud automation Cloud - Atlassian Support If a field or value doesn't exist, it will return an empty value:{{invalid reference}}. Learn about the concepts and procedures related to automation in Jira Cloud. 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}}. Used with the Related issues condition. You can access all fields of the parent. {{versions.name}}- Returns the name of the affects version. {{attachment.filename}}: Returns the filename of the attachment. 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) You must be a registered user to add a comment. Keep earning points to reach the top of the leaderboard. Can you provide a screenshot of your result? What I didn't notice, is that I entered the value: {{issue.sprint.name}}. There should be a locked field named either "Request Type" or "Customer Request Type" there. Join now to unlock these features and more. 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, 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, Automation for Jira documentation for Jira Server. {{changelog.summary}} - Changelog information for theSummaryfield. {{flags.name}} returns the name of the feature flag. {{issue. 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. A build represents the process in which files are converted into their final consumable form. ^ I tested this with Issues that had been in a previous Sprint, and were in the new Sprint being started - and the rule was successful, enteringonlythe new Sprint's name into the Description field, no old Sprint names. What third-party applications can I integrate with? This value won't work for any other trigger, even if a comment was added as a result (e.g. 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. Examples of how you can use smart values to manipulate and format dates in your Jira automation rules. The active issue. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. For example, you might count how many issues have a . You can access all fields of the parent. Smart Commit examples to use with Git and Automation for Jira {{issue.watchers.displayName}} - Returns the watcher's display name. General triggers include: Field value changed - when a field value is changed Form submitted - when forms attached to an issue are submitted Learn about the concepts and procedures related to automation in Jira Cloud. Added by: Jira Triggers that edit an issue, All the fields that were changed. Are you looking for server documentation? {{issue.Request Type.requestType.name}} - Returns the customer request type. For more information on when issues is available, seeRun a rule against issues in bulk. All of the issues found by the trigger are then treated as a single bundle of issues. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. {{createdBranches.name}} - returns the names of the branches, {{createdBranches.url}} - returns the URLs of the branches. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. {{attachment.author}}: Returnsthe user who added the attachment. There is no Jira smart value referring to approval name (so that we can differentiate when there are multiple approvals in a workflow). The trigger for automation is starting a new sprint (trigger = start sprint). Every rule starts with a trigger. TEST-123-some-feature, {{branch.url}} returns the URL of the branch, e.g. Accesses information relating to the sprint that triggered the rule. Smart values allow you to access and manipulate a wide range of issue data within your site. All of the issues found by the trigger are then treated as a single bundle of issues. {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. Do more to earn more! Can you please assist us in working out the following issues? 2020-07-20T07:00:00.0+0000. {{issue.key}} - Returns the issue's key, which is a unique identifier comprised of the project key and the issue's number. They can add significant power and complexity to your rules. 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 below example, we list each fix version that the issue has been added to, followed by the version's release date, in bullet point form. You can also trigger rules to run from third party services like Bitbucket or GitHub. {{pullRequest.sourceBranch}} returns the name of the source branch, e.g. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. What goes around comes around! The URL to access the issue. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. Go to templates. Reviewing your audit logs is an effective way of debugging your rules. Is there any information on the web available about the "{{#if functionality)? 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. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. Affects version of an issue as a list. Join the Kudos program to earn points and save your progress. {{comment.visibility.type}} - Returns the comment restriction type if any, e.g. 4877576. Do you have any idea how I find active sprint smart value? Triggers: Triggers wait for defined events to take place in your Jira instance and will then execute the automation rule. If multiple values are changed (e.g. Share the love by gifting kudos to your peers. Thanks for sharing the link back in this question, it might help others in future! 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.). {{version.name}} - Returns the version's name. Used with: any triggers that edit an issue. See all smart values that take issue fields and convert them into JSON format. {{commit.repository.url}} returns the repositorys URL. {{version.released}} - Returnstrue if the version is released, andfalse if not. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. In this case, we want to perform an action on the parent of the sub-task so in the dropdown menu, we choose Parent. You can access the current watchers of an issue. We will ensure the story points of the parent and sub-task always remain in sync. {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). See all smart values related to accessing Jira project details. Issues in Jira rarely exist in isolation. For example, you can set up your rule to only escalate an issue if it is high priority. Jira Software Automation: Basics & Common Use Cases - Atlassian If multiple values are changed (e.g. Note that repository contains additional nested smart values. {{approval.addedApprovers}} - Returns the set of approvers added to issue. Smart values in Jira automation | Cloud automation Cloud | Atlassian To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. 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. If this issue is in an Epic, then epic refers to the Epic issue. Accesses information fromJira Service Managementrequests. {{deployment.environment}} returns information related to the deployment environment. {{pullRequest.destinationBranch.repository}} returns information related to the destination branchs repository. In progress. Learn more about using smart values with sections and lists. Your image appears to show too many curly-brackets around the value. They allow you to access and manipulate almost any data in Jira. {{deployment.state}} returns the state of the deployment. 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. {{issue.resolution}} - Returns the issue's resolution. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. There should be a locked field named either "Request Type" or "Customer Request Type" there. global admin section. Can be combined with other date and time smart values. {{issue.security.name}} - Returns the security level name. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. You can access all fields of the Epic. Solved: Smart value of trigger issue in automation Smart values are variables that you can use in automation action configuration parameters. Used to access the values in an issue'sFix Versionsfield. [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. Each field is a list of changes. Which Jira-server version supports the use of smart value: "{{#if . }} {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. Can be combined with other date smart values. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. This value supports Date and Time functions. This can be almost anything you want. Learn how to use these to interact with Jiras REST API. {{branch.repository.url}} returns the URL, e.g. Story points are integral for many agile teams. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. Learn more about using smart values with sections and lists. This example returns an issue's previous type, after it has been changed. Learn more about using smart values with sections and lists. {{issue.assignee.displayName}} - Returns the issue's assignee. They enable customizing automation actions to be useful for your team and your customers. {{addedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to addition of a value. The three properties above can also be added to this, for example,{{issue.affectedServices.dependentServices.tier}} will return the dependent services' tiers. {{changelog.issuetype}} - Changelog information for theIssue type field. 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. 2020-07-20T07:00:00.0+0000. 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. If you've already registered, sign in. 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 . 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. Each DevOps trigger makes relevant smart values available, related to commits, changesets, committer users . This re-fetches the latest state of the issue from Jira. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. When an epic is marked as done move all of its stories to done also. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. Join the Kudos program to earn points and save your progress. Your smart value must identify a specific attachment for this to work. If a customer has not responded to an issue in 5 days, close the issue and leave a comment. {{issue.url}} - Returns the URL of the issue. Smart values are one of the most potent ways to do so. {{issue.project}} - the project this issue is a part of. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Used by triggers that involve adding a comment, such as Issue commented, Issue transitioned, or Issue updated. @Simeon Ross - Any ideas on this one? {{commit.repository.name}} returns the name of the repository, e.g. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. You can check this by navigating to the "Custom fields" page in theglobal admin section. - Any ideas on this one? You can check this by navigating to the "Custom fields" page in the. {{sprint.name}} - Returns the sprint name. {{comment.created}} - Returns the date and time of the comment. https://bitbucket.org/account/repo/TEST-123-some-feature. {{issue.InsightField}} - Returns the issue summary and issue key, {{issue.InsightField.key}} - Returns the issue key, {{issue.InsightField.summary}} - Returns the issue summary. {{issue.affectedServices.tier}} - Returns the tiers of the issue's Affected services. Accesses information for the version that triggered the rule. {{sprint.completeDate}} -Returns date the sprint was marked as complete. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. 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. 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. And the rule itself? 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). {{issue.watchers.emailAddress}} - Returns the watcher's email address. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. For Jira Service Management requests only. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{version.project.key}} - Returns the project key of the project the version belongs to. 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. Or you could count how many issues have the same label, same fixVersion, etc. For more information on this, see Configuring a webhook later on this page. it is not supported in server version now. See all smart values related to user fields, such as Reporter or Assignee. Thisshould not be usedsince it requires an expensive reload of issue data. {{environment.name}} returns the use-provided name for the environment, e.g. {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. Get answers to your question from experts in the community, Smart value of trigger issue in automation. Learn more about list smart values. Affects version of an issue as a list. Returns the value of the Jira Service Managements scale custom field. Is the IF statement available for Server version? Learn more about user smart values. {{version.startDate}} - Returns the version's start date. Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms. Wonderful :). 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. All of the issues found by the trigger are then treated as a single bundle of issues. Learn more about services in Jira Service Management, Learn more about configuring time tracking. 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. These smart values are only available for the Branch created development trigger. text {{/}}, or is this a Jira-cloud only functionality ? These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. 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. 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. Every rule starts with a trigger. As for if and when the support will go to server, I have no idea. Connect your source code management, build or deployment tool to use these smart values. What goes around comes around! We use the following smart-value to sum up story points from all sub-tasks: {{issue.subtasks.Story Points.sum}}. However sometimes the two fields holds the same person, resulting in an email with twice the same name. For more information on when issues is available, seeRun a rule against issues in bulk. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. {{versions.archived}}- Returnstrueif the affects version is archived, andfalseif not. I'll ask one of their team to update you here. {{comment.author}} - Returns the ID of comment's author. Use an IDE like Visual Studio Code to find the path. Because this smart value deals with multiple items (i.e: issues can have many components), it can be used with the#symbol to apply the rule to each individual component. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). Returns information related to all feature flags created in throughout the rule or branch, as a list. issue The active issue. Field value changed Available in Server Lite: No global admin section. 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).