{{rule.actor}} - Accesses the rule actor user. Set the Equals condition to true. Thisshould not be usedsince it requires an expensive reload of issue data. For example, you might count how many issues have a . Learn more about date and time smart values. You can access all fields of the Epic. They can add significant power and complexity to your rules. Accesses the details of a subtask's parent issue. . Whenever you want to edit a field in Jira, use the Edit issue action. Jira Automation: Building New Rules in 5 Easy Steps - Hevo Data The rule is running too quickly after the issue is created. I am glad to learn that helped you. Triggers can be set to run manually, based on a condition you set or scheduled. {{sprint.endDate}} -Returns the end date of the sprint. {{issue.description}} - Returns the content in the issue'sDescriptionfield. Join now to unlock these features and more. Join the Kudos program to earn points and save your progress. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. Properties are frequently used by add-ons and integrations to store values, 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. If you have multiple webhook responses, you can add the#symbol to apply the rule to each individual response. {{comment.created}} - Returns the date and time of the comment. Jira Automation: Get the Basics Right [2023] - iDalko 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. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. 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. 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. Is there a smart value that returns me only the name of the trigger sprint or at least only the name of the open sprint? {{issue.comments.size}} - Returns the number of comments on the issue. {{versions.description}}- Returns the description of the affects version. OMGYou're right. Learn about the concepts and procedures related to automation in Jira Cloud. In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. These smart values are only available for the Branch created development trigger. Thank you@Bill Sheboy for answer,The custom field is a Date Picker type. for a select field. Affects version of an issue as a list. Automation is a great way to reduce the manual work of keeping story points up to date. And we have lots more automation templates and guides for you to use and learn from in the automation template library. 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. {{pullRequest.destinationBranch}} returns the name of the destination branch, e.g.master, {{pullRequest.destinationBranch.url}} returns the URL of the destination branch, e.g. {{versions.name}}- Returns the name of the affects version. These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. {{createdBranches.product}} - returns the products that the branches were created in. Click Create a webhook. The three properties above can also be added to this, for example,{{issue.affectedServices.dependentServices.tier}} will return the dependent services' tiers. These smart values are only available for the Pull request created, Pull request declined and Pull request mergedtriggers. {{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. Jira smart values - issues | Automation for Jira Data Center and Server Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . Select the Issue fields condition from the New condition drop-down menu. When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. For example, checking that all sub-tasks of a parent issue are resolved. action: log to the audit file this value. Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms. {{issue.comments.last.body}} - Returns the body of the last comment. 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 p. Used with the Version created, Version updated, and Version released triggers. What I didn't notice, is that I entered the value: {{issue.sprint.name}}. Every rule starts with a trigger. Approval required: accesses information when an issue that requires approval is created or updated, or when new approvers are added to an issue. 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. "sd.public.comment".internal}} -. Approval completed: accesses information for an approval when an approval step on an issue is accepted or declined. 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. 7, {{deployment.url}} returns the absolute URL of the deployment, e.g. all fields available to{{issue}}are available here as well. After testing, disable both the HTTP dump and access logs to avoid performance issues. There are many ways you can edit a field. When an issue is raised without an assignee, auto-assign to whoever created it. For example, you can set up your rule to only escalate an issue if it is high priority. This example returns the new value of an issue'sSummary field after it has been changed. Can be combined with other user smart values. 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. This value supportsDate and Time functions, e.g. I've not been able to find such kind of information. These smart values are only available for the Build successful, Build failed and Build status changed development triggers. Learn more about using smart values with sections and lists. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{approval.decision}} - Returns the final decision of the approval. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. {{pullRequest.destinationBranch}} returns information related to the destination branch of the pull request. [property]}} And the rule itself? Jira smart values - issues | Cloud automation Cloud - Atlassian Support Affects version of an issue as a list. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). You can view the status of an automation rule to identify if the rule is currently active or not. Can be combined with other date smart values. Accesses the values in an issue'sAffected services field. This smart value only works for issues that have been added to an epic. Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. On successful request, you will be able access webhook response data using the available smart values. Please raise suggestion ticket in our public tracker, https://jira.atlassian.com/projects/JIRAAUTOSERVER. You can view the audit log of an individual rule, project-wide or at a global level. 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.). Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. {{issue.timetracking.remainingestimate}} - Returns the value in the Time remaining field. Please try just two around each side: Of note: what is the type of your field? I suspect not. First, you need a sample from the webhook payload data. Learn more about using smart values with sections and lists. Solved: Smart value use of "{{#if }} does not seem to {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. {{createdBranches.name}} - returns the names of the branches, {{createdBranches.url}} - returns the URLs of the branches. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. {{build.name}} returns the name of the build, e.g. {{flags.name}} returns the name of the feature flag. {{issue.security.name}} - Returns the security level name. E.g. Learn more about user smart values. Smart values allow you to access issue data within Jira. Instead using Re-fetch for Cloud slows the rule for about 1 second (or more). Available anywhere smart values are supported, to access the value of a field that has changed. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). "sd.public.comment".internal}}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. [property]}}, you can also access custom field information on your issues. 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. Here, we choose the Issue fields' condition and clarify that the issue type we are looking out for is a sub-task. It is better to use this than name as it cannot be changed. Is there any information on the web available about the "{{#if functionality)? A representation of a release/version in Jira. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). Prints the issue key and its status (e.g. 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. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. {{approval}} - Returns the name of the approval. For example, when setting multiple Fix Versions, then you can iterate over these using{{#changelog.fixVersion}}{{toString}}. This re-fetches the latest state of the issue from Jira. Jira smart values in automation rules. my-custom-prod-env, {{environment.type}} returns the environment type. @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 ! Used with: any triggers that edit an issue. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. Jira Software Automation: Basics & Common Use Cases - Atlassian for a select field. This is how you would return multiple responses using the smart value: Accesses information for a worklog entry that has just been logged against an issue. Conditions allow you to narrow the scope of your rule. {{commit.repository.name}} returns the name of the repository, e.g. A selection of smart values make Jira issue details readily available for Automation for Jira rules. Suggestion re: {{approval}} Smart Value and subfields - Atlassian 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. Note that repository contains additional nested smart values. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. Smart values allow you to access and manipulate a wide range of issue data within your site. Smart Commit examples to use with Git and Automation for Jira This smart value accesses the changelog, and a list of changes for each field. Can you provide a screenshot of your result? Now whenever this field changes in Jira, this automation rule kicks in. The rule actor is the user who executes a rule. Available only for the pull request created trigger. The status of a rule can be seen on its details screen. Note that repository contains additional nested smart values. They enable customizing automation actions to be useful for your team and your customers. The trigger for automation is starting a new sprint (trigger = start sprint). Select Automations - Create Rule. 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. 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}}. I would like the value that enters the text field to be the name of the sprint that created the trigger. [xxx].size}}: Returnsthe file size of a specific attachment. Advanced automation in Jira Service Desk - TMC Application Lifecycle {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. {{sprint.isStarted}} - Returnstrue if the sprint has started, andfalse if not. @Simeon Ross - Any ideas on this one? The rule triggers on 'Issue created' and is followed by the 'Send web request' component. In the project menu, click on Project Settings. They allow you to access . All of the issues found by the trigger are then treated as a single bundle of issues. Get answers to your question from experts in the community, Automation JQL condition: using smart values. 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. You can check this by navigating to the "Custom fields" page in the. Accesses information related to a file attachment on an issue. - theIssue transitionedtrigger). Learn more about automation triggers. 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 all fields of the Epic. {{sprint.name}} - Returns the sprint name. Learn more about services in Jira Service Management. {{comment.properties}} - Accesses any comment property. Can be combined with other date and time smart values. You could then use this to count the number of issues returned. Learn more about configuring time tracking. 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. 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. A branch represents an independent line of development. role. Examples of using smart values with lists. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. Smart values are one of the most potent ways to do so. {{issue.watchers.emailAddress}} - Returns the watcher's email address. Accesses information relating to the sprint that triggered the rule. Join the Kudos program to earn points and save your progress. See all smart values that can access and manipulate text fields, such as issue summary or comments. Issues in Jira rarely exist in isolation. Affects version of an issue as a list. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. Learn more about using smart values with sections and lists. {{issue.Story Points}} - Returns the issue's story point estimate (company-managed Jira Software Cloud only). Special conditions and actions are available to create powerful rules that can work across complex issue relationships. If a rule is inactive, it will not execute until it is enabled. To get a property in it, we should use{{webhookData.someValue.childValue}}. This value supports Date and Time functions. {{pullRequest.createdDate}} returns the time (UTC) when the pull request was created, e.g. See all smart values that are used to insert and format numerical values using math expressions. {{fieldChange.to}}Returns the new raw value, e.g. All of the issues found by the trigger are then treated as a single bundle of issues. {{sprint.startDate}} - Returns the start date of the sprint. 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. Challenges come and go, but your rewards stay with you. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. Using this branch component, we can move away from the main trunk of the rule and work on related issues. 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. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. Each DevOps trigger makes relevant smart values available, related to commits, changesets, committer users . FR Jira Dev Aug 05, 2021 I currently have an Automation workflow that creates multiple tasks and subtasks. Thanks for sharing the link back in this question, it might help others in future! They kick off the execution of your rules. {{issue.project}} - the project this issue is a part of. View topic Examples of using math expression smart values ISSUE-12: Fix bugs, {{pullRequest.url}} returns the absolute URL of the pull request, e.g.https://bitbucket.org/pull-request/182. 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. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. {{sprint.isClosed}} -Returnstrueif the sprint has closed, andfalseif not. {{comment.visibility.type}} - Returns the comment restriction type if any, e.g. {{pullRequest.sourceBranch}} returns information related to the source branch for the pull request. {{flags.key}} returns the key of the feature flag. {{changelog.summary}} - Changelog information for theSummaryfield. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. Automation is currently available in Jira Software Cloud and Confluence Cloud. In progress. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. A list of issues that have been created in the rule. Do you have any idea how I find active sprint smart value? The issue is not so much with the smart values itself, but with the {{#if }} statement. 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. {{commit.repository.url}} returns the repositorys URL. If you've already registered, sign in. Here you can access any issue property. {{attachment. See all smart values related to accessing Jira project details. Added by: Jira Triggers that edit an issue, All the fields that were changed. {{commit.shortHash}} returns the truncated SHA1 hash of the commit, e.g. To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. Acording with the documentation, Automation JQL condition suport smart values. Now whenever the story points of a sub-task changes, it will be reflected in the parent issue. For example,jira:issue_updated :issue_commented. 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. The following smart values are available to access and format development information from a connected source code management tool. {{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). Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. The smartvalue{{webhookData}}gets the root of the JSON payload. {{deletedFieldChanged.values}} - Returns the value/values deleted. global admin section. I recall there are suggestions in the backlog to add "wait until the prior step finishes" or "delay X seconds" actions. Accesses a Tempo Account field's properties. 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. Used with: the Create feature flag in LaunchDarkly action. If youre an Automation for Jira app customer on a server product, check out the Automation for Jira documentation for Jira Server. {{issue.url}} - Returns the URL of the issue. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. Learn more about using smart values with sections and lists. {{createdBranch.name}} - returns the name of the branch, {{createdBranch.url}} - returns the URL of the branch. See all smart values related to Assets in Jira Service Management Cloud. Added by: Jira Triggers that edit an issue, All the fields that were changed. {{versions.archived}}- Returnstrueif the affects version is archived, andfalseif not. If this issue is a sub-task, then parent refers to the parent issue. It resets every quarter so you always have a chance! Each field is a list of changes. Create an issue and update the Insight custom field with the object that have User attribute updated with portal only customer , and also add the portal only customer as reporter. [Custom Field]}} - Returns the value in an epic's custom field. Learn more about date and time smart values. Whenever you want to edit a field in Jira, use the 'Edit issue' action. Find issues that have the same custom field date as trigger issue. We do not currently support accessing fields within insight objects. Learn more about date and time smart values. {{deletedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to deletion of a value. If this issue is in an Epic, then epic refers to the Epic issue. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. Solved: Smart value of trigger issue in automation this is only available for some triggers. If you've already registered, sign in. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. You can also trigger rules to run from third party services like Bitbucket or GitHub. See all smart values that access and manipulate Jira issue data such as sprint, parent, or version. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). Possible states include pending, in_progress, successful, failed, cancelled, or unknown. {{sprint.completeDate}} -Returns date the sprint was marked as complete. Otherwise, register and sign in. Do more to earn more! Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. https://bitbucket.org/account/repo. See all smart values that can manipulate the values of items in a list. See all Jira Cloud automation smart values related to date and time. {addedfieldChange.field}} - Returns the field which has changed due to addition of a value. You must be a registered user to add a comment. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. Your image appears to show too many curly-brackets around the value. Or you could count how many issues have the same label, same fixVersion, etc. Each of your rules will have an audit log that you can review to see when the rule was triggered, the final result of the execution, and any actions that may have been performed. 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. Otherwise, register and sign in.