{{deletedFieldChanged.values}} - Returns the value/values deleted. Conditions allow you to narrow the scope of your rule. 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. Share the love by gifting kudos to your peers. 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. 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. When an epic is marked as done move all of its stories to done also. This smart value only works for issues that have been added to an epic. {{commit.repository.url}} returns the repositorys URL. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. {{version.name}} - Returns the version's name. You could then use this to count the number of issues returned. Learn about the concepts and procedures related to automation in Jira Cloud. [Custom Field].defaultValue}} - Returns the value displayed on first view of the field. {{version.description}} - Returns the version's description. See all smart values related to user fields, such as Reporter or Assignee. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. It some places it pops up, but there is no real explanation. OMGYou're right. For example, {{attachment.first.size}} will return the file size of the first attachment. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. For example, if the Assignee of a field changes, you could add a comment to the issue to note who the previous assignee was, and who the new assignee is. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). View the list of available triggers. all fields available to{{issue}}are available here as well. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. See all smart values that can manipulate the values of items in a list. Accesses a Tempo Account field's properties. A commit represents an individual change to a file (or set of files). for a select field. These smart values are only available for the Pull request created, Pull request declined and Pull request mergedtriggers. Used to access the values in an issue'sFix Versionsfield. They allow you to access and manipulate almost any data in Jira. They allow you to automate tasks and make changes within your site. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. Otherwise, register and sign in. This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. 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. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). You can view the status of an automation rule to identify if the rule is currently active or not. Hi John, thanks a lot for your quick response. We will ensure the story points of the parent and sub-task always remain in sync. I'll mention the docs discrepancies to the person that maintains our documentation. 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. 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). See all smart values that access and manipulate Jira issue data such as sprint, parent, or version. 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}}. Only one word but It changes the whole picture. See all smart values related to builds, deployments, and source code management. 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. {{issue. for a select field. Challenges come and go, but your rewards stay with you. Accesses information for the current running rule. Challenges come and go, but your rewards stay with you. 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. all fields available to{{issue}}are available here as well. If a rule is inactive, it will not execute until it is enabled. However sometimes the two fields holds the same person, resulting in an email with twice the same name. Is there any information on the web available about the "{{#if functionality)? You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. 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. 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. Learn more about date and time smart values. {{issue. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. {{commit.shortHash}} returns the truncated SHA1 hash of the commit, e.g. it is not supported in server version now. The following smart values are available to access and format development information from a connected source code management tool. 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. Or .displayName if accountId doe not work as hoped. General triggers These triggers can be used across all Jira products. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. Examples of using smart values with text strings. Accesses time tracking estimates. Keep earning points to reach the top of the leaderboard. At the same time, it would be to good to mention that it is Jira-cloud functionality only. Accesses the previous issue created in the rule. Summary Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. {{attachment.filename}}: Returns the filename of the attachment. Understand the general concepts and best practices of automation in Atlassian Cloud products. Properties are frequently used by add-ons and integrations to store values, 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. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. issue The active issue. You can view the audit log of an individual rule, project-wide or at a global level. There are many ways you can edit a field. Learn about the concepts and procedures related to automation in Jira Cloud, Smart values allow you to access issue data within Jira. We do not currently support accessing fields within insight objects. {{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue. After testing, disable both the HTTP dump and access logs to avoid performance issues. {{issue.comments.author.displayName}} - Returns the comment authors. {{attachment.author.accountId}}: Returnsthe ID associated with the user name. {{attachment. 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. Affects version of an issue as a list. For example, checking that all sub-tasks of a parent issue are resolved. You can check this by navigating to the "Custom fields" page in the. For example, when an issue is transitioned you can see what status the issue transitioned from. global admin section. You could then use this to count the number of issues returned. build#123, {{build.url}} returns the absolute URL of the build, e.g. Added by: Sprint created, started or completed triggers. Set the Equals condition to true. {{issue.project}} - the project this issue is a part of. : To do,In progress, orDone). See all smart values related to Assets in Jira Service Management Cloud. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. Can you please assist us in working out the following issues? For example, you can set up your rule to only escalate an issue if it is high priority. Used to access information about an issue's epic. {{comment.internal}} - forJira Service Management comments, returns false if the comment is visible to customers. {{fieldChange.to}}Returns the new raw value, e.g. What third-party applications can I integrate with? Accesses information fromJira Service Managementrequests. {{comment.properties}} - Accesses any comment property. Please try just two around each side: Of note: what is the type of your field? Is there a way to similar functionality in Jira-Server? {{issue.epic.key}} - Returns the epic's key, e.g. Or you could count how many issues have the same label, same fixVersion, etc. Now whenever this field changes in Jira, this automation rule kicks 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) The issue is not so much with the smart values itself, but with the {{#if }} statement. {{versions.name}}- Returns the name of the affects version. {{issue.affectedServices.name}} - Returns the names of the issue's Affected services. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. {{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. Each field is a list of changes. {{flags.name}} returns the name of the feature flag. 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. global admin section. {{issue. 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. However sometimes the two fields holds the same p. 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. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. {{deployment.state}} returns the state of the deployment. 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. Click Create a webhook. https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}. Can you provide a screenshot of your result? You must be a registered user to add a comment. {{branch.repository}} returns information related to the repository the branch belongs to. {{version.released}} - Returnstrue if the version is released, andfalse if not. Smart values are one of the most potent ways to do so. Thank you@Bill Sheboy for answer,The custom field is a Date Picker type. https://bitbucket.org/account/repo/TEST-123-some-feature. {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. {{build.refs}} returns the refs of the build, e.g. Thanks for sharing the link back in this question, it might help others in future! {{comment.body}} - Returns the body of the comment that triggered the rule. 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! It resets every quarter so you always have a chance! . {{rule.actor}} - Accesses the rule actor user. Smart values are variables that you can use in automation action configuration parameters. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. {{versions.releaseDate}}- Returns the affects version's release date. {{issue.url}} - Returns the URL of the issue. For example, you might count how many issues have a priority of 'highest' and then send an alert. {{addedfieldChange.values}} - Returns the new value/values added. Returns the value of the Jira Service Managements scale custom field. If you have multiple webhook responses, you can add the#symbol to apply the rule to each individual response. 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. Can be combined with other date and time smart values. 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. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. See all smart values that can access and manipulate text fields, such as issue summary or comments. Select the Issue fields condition from the New condition drop-down menu. 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. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. {{approval.addedApprovers}} - Returns the set of approvers added to issue. [Custom Field]}} - Returns the value in an epic's custom field. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. These smart values can only be accessed through other root keys (e.g. https://bitbucket.org/account/repo. They enable customizing automation actions to be useful for your team and your customers. Or you could count how many issues have the same label, same fixVersion, etc. [Custom Field].name}} - Returns the visible label displayed on the left of the field. {{pullRequest.destinationBranch}} returns information related to the destination branch of the pull request. 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. All of the issues found by the trigger are then treated as a single bundle of issues. Accesses the values in an issue'sAffected services field. 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. In progress. Connect your source code management, build or deployment tool to use these smart values. Check out how we use smart values in our Jira automation template library. The following example prints all the issue keys returned from the JQL search, in bullet point form. 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. {{commit.repository.name}} returns the name of the repository, e.g. There should be a locked field named either "Request Type" or "Customer Request Type" there. {{attachment.author.timeZone}}: Returns the timezone the user is registered being in; this doesn't change dynamically based upon where the user logs in from, it is the timeZone registered in their user account. There should be a locked field named either "Request Type" or "Customer Request Type" there. The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. Note that repository contains additional nested smart values. Now whenever the story points of a sub-task changes, it will be reflected in the parent issue. Automation is a great way to reduce the manual work of keeping story points up to date. For example, PROJ-123. 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. 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). text {{/}}, or is this a Jira-cloud only functionality ? The active issue. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Note that environment contains additional nested smart values. Examples of how you can use smart values to manipulate and format dates in your Jira automation rules. Access information related to all branches created in the rule, as a list. {{version.releaseDate}} - Returns the version's release date. In your site, the rule actor will be set as Automation app user. {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. {{issue.fixVersions.description}} - Returns the description of the fix version. {{sprint.startDate}} - Returns the start date of the sprint. These can be combined with other date and time smart values. {{comment.properties. Challenges come and go, but your rewards stay with you. {{webhookResponse.status}} - response code e.g. To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. Access information related to the last branch that was created.