Refers to the original issue that triggered the rule; used when you branch the chain. These smart values are only available for the Commit created development trigger. This applies to the legacy Insight app. {{issue.fixVersions.description}} - Returns the description of the fix version. To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. This smart value only works for issues that have been added to an epic. 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. Check out how we use smart values in our Jira automation template library. This re-fetches the latest state of the issue from Jira. Join the Kudos program to earn points and save your progress. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. 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. You're on your way to the next level! for a select 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. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. [Custom Field]}} - Returns the value in an epic's custom field. Can be combined with other user smart values. Your image appears to show too many curly-brackets around the value. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. See all smart values that are used to insert and format numerical values using math expressions. Click Create a webhook. The rule is running too quickly after the issue is created. Otherwise, register and sign in. The smartvalue{{webhookData}}gets the root of the JSON payload. These smart values can only be accessed through other root keys (e.g{{deployment.environment}}). Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. {{sprint.goal}} - Returns the sprint goal. {{createdBranches.product}} - returns the products that the branches were created in. Otherwise, register and sign in. Can be combined with other date and time smart values. {{commit.repository}} returns the information related to the repository. This is a list of metadata that can be associated with a build. For more information on when issues is available, seeRun a rule against issues in bulk. You can check this by navigating to the "Custom fields" page in theglobal admin section. For example, wheninvalid referencedoesn't contain a value, you can printHello worldusing{{invalid reference|"Hello world"}}. There is no Jira smart value referring to approval name (so that we can differentiate when there are multiple approvals in a workflow). Jira smart values in automation rules. Learn more about configuring time tracking. Using this branch component, we can move away from the main trunk of the rule and work on related issues. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. If multiple values are changed (e.g. For example, you might count how many issues have a priority of 'highest' and then send an alert. https://bitbucket.org/account/repo. Used with the Related issues condition. To get a concrete example, let's consider the payload below: Here are some examples of ways to test the JSON path to get the right data in the smart values, so you can get it right on your first try! This value supports Date and Time functions. {{sprint.endDate}} -Returns the end date of the sprint. Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. {{createdBranch.repository.url}} - returns the repositorys URL. {fieldChange.toString}}- Returns the new value as displayed. Learn more about using smart values with sections and lists. They enable customizing automation actions to be useful for your team and your customers. build#123, {{build.url}} returns the absolute URL of the build, e.g. The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. {{comment.body}} - Returns the body of the comment that triggered the rule. It may contain, for example, branches and tags names.This value is optional and may be an empty list. Affects version of an issue as a list. {{attachment.author}}: Returnsthe user who added the attachment. Do you have any idea how I find active sprint smart value? all fields available to{{issue}}are available here as well. 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. 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. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. The active issue. 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. See all smart values that can manipulate the values of items in a list. If you've already registered, sign in. role. 2020-07-20T07:00:00.0+0000. {{sprint.name}} - Returns the sprint name. 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) Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. E.g. {{issue.status}} - Returns the issue's status, {{issue.status.name}} - Returns the issue's status, {{issue.summary}} - Returns the issue's summary, {{issue.versions}} - Returns the issue'sAffects versions. awesome commit handles everything, {{commit.url}} returns the absolute URL of the commit, e.g. Used to access information about an issue's epic. Accesses information for the version that triggered the rule. You can also trigger rules to run from third party services like Bitbucket or GitHub. 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. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. {{attachment.author.accountId}}: Returnsthe ID associated with the user name. 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. I suspect not. {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). It resets every quarter so you always have a chance! The following smart values are available to access and format development information from a connected source code management tool. They allow you to automate tasks and make changes within your site. Note that repository contains additional nested smart values. {{issue.fix.Versions.archived}} - Returns true if the fix version is archived, andfalse if not. You can specify a default value to prevent this. Only one word but It changes the whole picture. Go to templates. . You could then use this to count the number of issues returned. [property]}} You could then use this to count the number of issues returned. But it looks like functionality for the Jira cloud version. {{issue.components.name}}- Returns the values in the issue'sComponentfield. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. They often contain sub-tasks, are stories that are part of a larger epic, or are simply linked to other issues using certain relationships. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (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. 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. {{issue.parent.key}} - Returns the issue key of the subtask's parent issue. For example, PROJ-123. 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! To get a property in it, we should use{{webhookData.someValue.childValue}}. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. {{issue.affectedServices.changeApprovers}}, {{issue.affectedServices.changeApprovers.displayName}}, {{issue.affectedServices.dependentServices}}, {{issue.affectedServices.dependentServices.tier}}, {{issue.Request Type.currentStatus.status}}, {{comment.properties. Fix versions of an issue as a list. They must be met for your rule to continue running. Join the Kudos program to earn points and save your progress. The active issue. Approval completed: accesses information for an approval when an approval step on an issue is accepted or declined. {{issue.security.id}} - Returns the security level ID. All of the issues found by the trigger are then treated as a single bundle of issues. It resets every quarter so you always have a chance! Would be good and useful functionality to have. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. Learn more about using smart values with sections and lists. 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). Access information related to all branches created in the rule, as a list. You can access all fields of the parent. There should be a locked field named either "Request Type" or "Customer Request Type" there. Note that environment contains additional nested smart values. {{environment.name}} returns the use-provided name for the environment, e.g. {{issue.Request Type.requestType.name}} - Returns the customer request type. The status of a rule can be seen on its details screen. You can also use this withlists. {{versions.releaseDate}}- Returns the affects version's release date. Accesses any issue property. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. Triggers, conditions, and actions are the building blocks of automation. [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. A pull request represents proposed changes before they are integrated into an official project. Share the love by gifting kudos to your peers. For smart values related to the Insight feature in Jira Service Management, see Jira smart values - Assets. Share the love by gifting kudos to your peers. Learn more about automation triggers. In your site, the rule actor will be set as Automation app user. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. {{attachment. Added by: Send web request with "Wait for response" checkedOn successful request, you will be able access webhook response data using the following smart values: Multiple responses can be access via the following fields: Added by: Worklogged TriggerThe worklog entry that has just been logged against an issue. You can access all fields of the Epic. You must be a registered user to add a comment. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- You can access all fields of the Epic. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. Share the love by gifting kudos to your peers. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. Properties are frequently used by add-ons and integrations to store values, e.g. Set the Equals condition to true. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. Automation is a great way to reduce the manual work of keeping story points up to date. - theIssue transitionedtrigger). {{issue.InsightField}} - Returns the issue summary and issue key, {{issue.InsightField.key}} - Returns the issue key, {{issue.InsightField.summary}} - Returns the issue summary. Used with the Version created, Version updated, and Version released triggers. Accesses an insight field's full name, key, or summary. It some places it pops up, but there is no real explanation. 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. Thisshould not be usedsince it requires an expensive reload of issue data. {{branch.repository}}). Learn more about user smart values. Is the IF statement available for Server version? {{issue.security.name}} - Returns the security level name. The trigger for automation is starting a new sprint (trigger = start sprint). Conditions allow you to narrow the scope of your rule. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. Do more to earn more! {{pullRequest.createdDate}} returns the time (UTC) when the pull request was created, e.g. Learn more about using smart values with sections and lists. This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. A list of issues that have been created in the rule. Can be combined with other user-related smart values. Accesses time tracking estimates. We will ensure the story points of the parent and sub-task always remain in sync. 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. Returns a list of issues from a JQL search caused bythe Lookup issues action. {{flags.key}} returns the key of the feature flag. 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). These smart values can only be accessed through other root keys (e.g. 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. A build represents the process in which files are converted into their final consumable form. {{commit.repository.url}} returns the repositorys URL. Join now to unlock these features and more. These can be combined with other user smart values. Can be combined with other date and time smart values. All of the issues found by the trigger are then treated as a single bundle of issues. {{issue.TempoAccountField}} - Returns the name of the account, {{issue.TempoAccountField.id}} - Returns the ID of the account, {{issue.TempoAccountField.name}} - Returns the name of the account, {{issue.TempoAccountField.value}} - Returns the name of the account, Can be used with: the Approval required trigger and the Approval completed trigger. If it has a time you may need to strip off the time part for the comparison by changing the format: {{triggerIssue.customfield_10043.jqlDate}}. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. 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: Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. "sd.public.comment".internal}} -. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. 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. Examples of using smart values with dates. A build represents the process in which files are converted into their final consumable form. {{issue.comments.size}} - Returns the number of comments on the issue. Refers to the original issue when you branch the chain. 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) Learn more about date and time smart values. {{issue.project}} - the project this issue is a part of. This was something we have added since the split and I suspect that the server team has not caught up. 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. Smart values are one of the most potent ways to do so. {{rule.name}} - Returns the name of the rule that is currently running. "sd.public.comment".internal}}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Examples of using smart values with lists. {{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. For example, checking that all sub-tasks of a parent issue are resolved. What third-party applications can I integrate with? Please try just two around each side: Of note: what is the type of your field? However sometimes the two fields holds the same p. Select the Issue fields condition from the New condition drop-down menu. Examples of using math expression smart values. 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. Examples of how you can use smart values to set the text value of an issues field, such as Summary or Description. 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. @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 !