The rule actor is the user who executes a rule. Added by: Jira Triggers that edit an issue, All the fields that were changed. 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. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. On successful request, you will be able access webhook response data using the available smart values. If this issue is a sub-task, then parent refers to the parent issue. This value won't work for any other trigger, even if a comment was added as a result (e.g. Triggers can be set to run manually, based on a condition you set or scheduled. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. {{approval}} - Returns the name of the approval. Used to access the values in an issue'sFix Versionsfield. Accesses the values in an issue'sAffected services field. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. Jira automation triggers | Automation for Jira Data Center - Atlassian {{issue. Is the IF statement available for Server version? If a customer has not responded to an issue in 5 days, close the issue and leave a comment. 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? You can access all fields of the Epic. {{pullRequest.title}} returns the title of the pull request, e.g. Field value changed Available in Server Lite: No {{comment.internal}} - forJira Service Management comments, returns false if the comment is visible to customers. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. These smart values are only available for the Branch created development trigger. The trigger for automation is starting a new sprint (trigger = start sprint). Is there any information on the web available about the "{{#if functionality)? 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. You can check this by navigating to the "Custom fields" page in theglobal admin section. I'll mention the docs discrepancies to the person that maintains our documentation. Smart values in Jira automation. 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. {{branch.name}} returns the name of the branch, e.g. "sd.public.comment".internal}} -. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. There are many ways you can edit a field. Accesses the details of a subtask's parent issue. {{sprint.completeDate}} -Returns date the sprint was marked as complete. 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. There should be a locked field named either "Request Type" or "Customer Request Type" there. This is a list of metadata that can be associated with a build. {{version.releaseDate}} - Returns the version's release date. 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. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. Used with the Version created, Version updated, and Version released triggers. What third-party applications can I integrate with? For more information on when issues is available, seeRun a rule against issues in bulk. {{fieldChange.to}}Returns the new raw value, e.g. Or you could count how many issues have the same label, same fixVersion, etc. What goes around comes around! Accesses a Tempo Account field's properties. {{branch.repository}}). Webhooks - Atlassian The active issue. The active issue. Accesses any issue property. {{issue.Request Type.requestType.name}} - Returns the customer request type. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. Go to templates. {{issue.fixVersions.name}} - Returns the name of the fix version. 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. 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. Refers to the original issue that triggered the rule; used when you branch the chain. {{build.refs}} returns the refs of the build, e.g. If multiple values are changed (e.g. Affects version of an issue as a list. Note that repository contains additional nested smart values. 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. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. Also provides the customer portal URL for Jira Service Management issues. {{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue. {{sprint.startDate}} - Returns the start date of the sprint. "sd.public.comment".internal}}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. After a lot of searches, I found the answer on: https://community.atlassian.com/t5/Jira-questions/Store-Active-Sprint-in-New-Field-Using-Jira-Automation-Script/qaq-p/1695408. See all smart values related to Assets in Jira Service Management Cloud. Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Examples of how you can use smart values to manipulate and format dates in your Jira automation rules. Smart values in Jira automation | Cloud automation Cloud | Atlassian . 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}}. To get a property in it, we should use{{webhookData.someValue.childValue}}. Awesome! Challenges come and go, but your rewards stay with you. The following example sums all of the story points for issues returned from the JQL search. What third-party applications can I integrate with? Your smart value must identify a specific attachment for this to work. 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}}. 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. {{issue.comments.size}} - Returns the number of comments on the issue. 2020-07-20T07:00:00.0+0000. Learn more about date and time smart values. {{fieldChange}}only contains the first changed value. Otherwise, register and sign in. {{commit.shortHash}} returns the truncated SHA1 hash of the commit, e.g. {{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. You can access the current watchers of an issue. 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. Learn more about date and time smart values. If more than one flag has been created throughout the rule, {{flag}} will return the most recently-created flag. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. All of the issues found by the trigger are then treated as a single bundle of issues. [Custom Field].defaultValue}} - Returns the value displayed on first view of the field. A commit represents an individual change to a file (or set of files). Used with: any triggers that edit an issue. Because this smart value deals with multiple items (i.e: issues can have many Affects versions), it can be used with the#symbol to apply the rule to each individual component. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. An environment represents a distinct ecosystem where products are deployed to. When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. {{flags.name}} returns the name of the feature flag. Learn more about using smart values with sections and lists. 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. Returns the value of the Jira Service Managements rate custom field. Each field is a list of changes. It is better to use this than name as it cannot be changed. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. Learn about the concepts and procedures related to automation in Jira Cloud. If a condition fails, the rule will stop running and no actions following the condition will be performed. {addedfieldChange.field}} - Returns the field which has changed due to addition of a value. 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. Accesses the previous issue created in the rule. {{versions.name}}- Returns the name of the affects version. Through the dot notation you can access fields like issue type, status and custom fields (details on how you can use these to interact with Jira's REST api are, A list of issues generated by a trigger that runs a JQL search (, trigger when set to process in bulk). ^ 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. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. Smart values are one of the most potent ways to do so. 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. For example, you might count how many issues have a priority of 'highest' and then send an alert. {{sprint.endDate}} -Returns the end date of the sprint. Keep earning points to reach the top of the leaderboard. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. Jira Automation: Building New Rules in 5 Easy Steps - Hevo Data Affects version of an issue as a list. action: log to the audit file this value. And the rule itself? Developers. Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. Each field is a list of changes. https://bitbucket.org/account/repo/TEST-123-some-feature, {{pullRequest.destinationBranch.repository}}, https://bitbucket.org/{7faf7dee-a29b-4faa-bbc2-d7128a6d3278}/{315a3ecb-1f18-4953-98ae-5890f93073b5}/addon/pipelines/home#!/results/7, [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work], https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool.