Understand the general concepts and best practices of automation in Atlassian Cloud products. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. {{issue.affectedServices.name}} - Returns the names of the issue's Affected services. Join now to unlock these features and more. {{comment.author}} - Returns the ID of comment's author. {{pullRequest.sourceBranch}} returns the name of the source branch, e.g. {{pullRequest.title}} returns the title of the pull request, e.g. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. {{addedfieldChange.values}} - Returns the new value/values added. {{changelog.summary}} - Changelog information for theSummaryfield. After testing, disable both the HTTP dump and access logs to avoid performance issues. 2020-07-20T07:00:00.0+0000. Smart values are variables that you can use in automation action configuration parameters. {{issue.security.name}} - Returns the security level name. {{deployment.environment}} returns information related to the deployment environment. {{createdBranches.product}} - returns the products that the branches were created in. Join now to unlock these features and more. {{commit.hash}} returns the SHA1 hash of the commit, e.g.4877576951f3eda43625d3345058e702dad3df0d. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. {{branch.repository.name}} returns the name of the repository. ISSUE-12: Fix bugs, {{pullRequest.url}} returns the absolute URL of the pull request, e.g.https://bitbucket.org/pull-request/182. Learn more about using smart values with sections and lists. Examples of how you can use smart values to manipulate and format dates in your Jira automation rules. my-awesome-repository. {fieldChange.fromString}} - Returns the previous value as displayed. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. What third-party applications can I integrate with? {{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. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. Challenges come and go, but your rewards stay with you. Learn more about using smart values with sections and lists. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. 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. Acording with the documentation, Automation JQL condition suport smart values. https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}. Accesses information for the current running rule. See all Jira Cloud automation smart values related to date and time. {{issue.assignee.displayName}} - Returns the issue's assignee. A build represents the process in which files are converted into their final consumable form. As for if and when the support will go to server, I have no idea. If this issue is a sub-task, then parent refers to the parent issue. Note that repository contains additional nested smart values. See all smart values related to Assets in Jira Service Management Cloud. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. Returns the value of the Jira Service Managements scale custom field. Challenges come and go, but your rewards stay with you. However, you can now change the rule actor for your automation rules. To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. global admin section. Used by triggers that involve adding a comment, such as Issue commented, Issue transitioned, or Issue updated. A repository represents a collection of files and associated metadata. role. Learn about the concepts and procedures related to automation in Jira Cloud, Smart values allow you to access issue data within Jira. https://bitbucket.org/{7faf7dee-a29b-4faa-bbc2-d7128a6d3278}/{315a3ecb-1f18-4953-98ae-5890f93073b5}/addon/pipelines/home#!/results/7, {{build.state}} returns the state of the build. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. Accesses time tracking estimates. 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. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. First, you need a sample from the webhook payload data. E.g. Join the Kudos program to earn points and save your progress. { {issue. See all smart values that access and manipulate Jira issue data such as sprint, parent, or version. Thisshould not be usedsince it requires an expensive reload of issue data. In this case, we want to perform an action on the parent of the sub-task so in the dropdown menu, we choose Parent. 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 . {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Is there a way to similar functionality in Jira-Server? Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. You can access all fields of the parent. 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). Seeaccesing multi-value fields, Added by: This is added any time an issue is added. You can specify a default value to prevent this. Each field is a list of changes. global admin section. This re-fetches the latest state of the issue from Jira. {{commit.message}} returns the commit message, e.g. This example returns an issue's previous type, after it has been changed. If you've already registered, sign in. OMGYou're right. Triggers can be set to run on a schedule, and can be customized before being applied to a rule. Can be combined with other user smart values. For Jira Service Management requests only. https://bitbucket.org/account/repo/TEST-123-some-feature. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). Please share more details and screenshots in order to be able to help you. View the list of available triggers. this is only available for some triggers. Can you please assist us in working out the following issues? Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. The trigger for automation is starting a new sprint (trigger = start sprint). {{deletedFieldChanged.values}} - Returns the value/values deleted. These smart values are only available for the Branch created development trigger. They kick off the execution of your rules. Used with: the Send web request action (Wait for response enabled). Here, we choose the Issue fields' condition and clarify that the issue type we are looking out for is a sub-task. If a rule is inactive, it will not execute until it is enabled. : To do,In progress, orDone). A list of issues that have been created in the rule. 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. 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. Learn how to integrate your source code management tool with Jira Cloud, Visit the marketplace to integrate your build or deployment tool with Jira Cloud. {{issue.parent.epic.summary}} - Returns the summary of the parent issue's epic. You can access the current watchers of an issue. 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. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. {{version.startDate}} - Returns the version's start date. You can access all fields of the parent. {{branch.repository.url}} returns the URL, e.g. {{sprint.endDate}} -Returns the end date of the sprint. Learn more about date smart values. 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. Or you could count how many issues have the same label, same fixVersion, etc. For example, when an issue is transitioned you can see what status the issue transitioned from. If you've already registered, sign in. {{approval}} - Returns the name of the approval. A condition refines the rule so it wont act too broadly. The trigger for automation is starting a new sprint (trigger = start sprint). Issues in Jira rarely exist in isolation. 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) Accesses information related to a file attachment on an issue. Affects version of an issue as a list. We do not currently support accessing fields within insight objects. Understand the general concepts and best practices of automation in Atlassian Cloud products. {{issue.parent.key}} - Returns the issue key of the subtask's parent issue. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. Would be good and useful functionality to have. {{createdBranch.repository.url}} - returns the repositorys URL. Returns a list of issues from a JQL search caused bythe Lookup issues action. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. Understand the general concepts and best practices of automation in Atlassian Cloud products. That is not the correct custom field id for the field you want. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. I'll ask one of their team to update you here. The legacy Insight App will reach end of service on March 31, 2022. You can view the audit log of an individual rule, project-wide or at a global level. This applies to the legacy Insight app. Added by: Sprint created, started or completed triggers. For more information on this, see Configuring a webhook later on this page. {{comment.created}} - Returns the date and time of the comment. Access information related to the last branch that was created. 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. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. This example returns the new value of an issue'sSummary field after it has been changed. Triggers, conditions, and actions are the building blocks of automation. Please raise suggestion ticket in our public tracker, https://jira.atlassian.com/projects/JIRAAUTOSERVER. {{createdBranches.repository.url}} - returns the URLs of each repository. Accesses a Tempo Account field's properties. You could then use this to count the number of issues returned. {{versions.releaseDate}}- Returns the affects version's release date. Refers to the original issue when you branch the chain. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. A selection of smart values make Jira issue details readily available for Automation for Jira rules. {{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. Learn more about using smart values with sections and lists. Your image appears to show too many curly-brackets around the value. Learn more about user smart values. {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. These can be combined with other user smart values. {{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). Also provides the customer portal URL for Jira Service Management issues. When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. {{issue.comments.last.body}} - Returns the body of the last comment. You can also trigger rules to run from third party services like Bitbucket or GitHub. You can set triggers to run on a schedule or as needed. {{pullRequest.sourceBranch}} returns information related to the source branch for the pull request.