Solved: Using Automation to Link issues in a workflow with I've tested it on my instance and it yielded only 1 sprint (out of 3 that are ongoing). Smart values allow you to access and manipulate a wide range of issue data within your site. 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. Accesses the details of a subtask's parent issue. What third-party applications can I integrate with? {{commit.repository.name}} returns the name of the repository, e.g. A branch represents an independent line of development. {{createdBranch.name}} - returns the name of the branch, {{createdBranch.url}} - returns the URL of the branch. Used with: the Clone issue, Create issue, and Create sub-tasks actions. You can specify a default value to prevent this. https://bitbucket.org/commit/121212, {{commit.isMergeCommit}} returns True if commit is a merge commit, {{commit.timestamp}} returns the timestamp (UTC) the commit was created. Fix versions of an issue as a list. Join the Kudos program to earn points and save your progress. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). The following smart values are available to access and format development information from a connected source code management tool. Acording with the documentation, Automation JQL condition suport smart values. 2020-07-20T07:00:00.0+0000. [property]}} You must be a registered user to add a comment. These can be combined with other date and time smart values. In the below example, we're sending out a notification that someone has added a comment to an issue, perhaps as a Slack message. Keep earning points to reach the top of the leaderboard. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. Note that repository contains additional nested smart values. If this issue is in an Epic, then epic refers to the Epic issue. Every rule starts with a trigger. In the form that is shown, enter the details for your new webhook. A good tip for checking your progress is to say aloud what you have built so far: Whenever the field value changes for story points AND it is a sub-task. {{issue.affectedServices.changeApprovers}}, {{issue.affectedServices.changeApprovers.displayName}}, {{issue.affectedServices.dependentServices}}, {{issue.affectedServices.dependentServices.tier}}, {{issue.Request Type.currentStatus.status}}, {{comment.properties. {{build.refs}} returns the refs of the build, e.g. Hi John, thanks a lot for your quick response. Keep earning points to reach the top of the leaderboard. Jira Software Questions Smart value of trigger issue in automation Smart value of trigger issue in automation Eliyahu Klein Jan 09, 2023 Hi, I created an automation that created a value in a short text field. my-custom-prod-env, {{environment.type}} returns the environment type. Your image appears to show too many curly-brackets around the value. A list of issues that have been created in the rule. Learn more about services in Jira Service Management, Learn more about configuring time tracking. 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. This smart value only works for issues that have been added to an epic. If this issue is a sub-task, then parent refers to the parent issue. {{issue.watchers.displayName}} - Returns the watcher's display name. You can also use this with, . Affects version of an issue as a list. Learn more about using smart values with sections and lists. Your thorough reply here helped me in a completely different use case. But it looks like functionality for the Jira cloud version. Suggestion re: {{approval}} Smart Value and subfields - Atlassian {{versions.name}}- Returns the name of the affects version. {{issue.timetracking.remainingestimate}} - Returns the value in the Time remaining field. 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. action: log to the audit file this value. These smart values can only be accessed through other root keys (e.g{{deployment.environment}}). If this issue is a sub-task, then parent refers to the parent issue. {{createdBranches.repository.url}} - returns the URLs of each repository. this is only available for some triggers. You can set triggers to run on a schedule or as needed. 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. Accesses time tracking estimates. Send a daily Slack message with a list of issues still open in the Sprint. For example, PROJ-123. {{pullRequest.sourceBranch}} returns the name of the source branch, e.g. Learn more about list smart values. {fieldChange.fromString}} - Returns the previous value as displayed. You can also use this with, . 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. {{commit.message}} returns the commit message, e.g. Try adding.accountId after coordinator (so{{#if(issue.assignee.equals(issue.coordinator.accountId))}}. Now whenever this field changes in Jira, this automation rule kicks in. A deployment represents the process in which a product is released in an environment. {{version.project.key}} - Returns the project key of the project the version belongs to. Actions are the doers of your rule. Returns a list of issues from a JQL search caused bythe Lookup issues action. After testing, disable both the HTTP dump and access logs to avoid performance issues. To get a property in it, we should use{{webhookData.someValue.childValue}}. Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. If a rule is inactive, it will not execute until it is enabled. 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}} Check out how we use smart values in our Jira automation template library. Learn more about list smart values. : To do,In progress, orDone). {{createdBranch.product}} - returns the product that the branch was created in (for example, Bitbucket). {{issue.affectedServices.dependentServices}}- Returns the list of services that this issue's services depend on. An environment represents a distinct ecosystem where products are deployed to. They can add significant power and complexity to your rules. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. Returns information related to all feature flags created in throughout the rule or branch, as a list. 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. Jira smart values - issues | Automation for Jira Data Center and Server Refers to the original issue when you branch the chain. You could then use this to count the number of issues returned. Approval completed: accesses information for an approval when an approval step on an issue is accepted or declined. {{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. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). Used with the Version created, Version updated, and Version released triggers. {{issue.security.name}} - Returns the security level name. The information that you can access on the issue are described in the Available properties section below. Thisshould not be usedsince it requires an expensive reload of issue data. 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) A repository represents a collection of files and associated metadata. Some issue properties are more complex, and theyve been described in their own sections on this page. There should be a locked field named either "Request Type" or "Customer Request Type" there. {{version.released}} - Returnstrue if the version is released, andfalse if not. issue The active issue. {{pullRequest.destinationBranch}} returns the name of the destination branch, e.g.master, {{pullRequest.destinationBranch.url}} returns the URL of the destination branch, e.g. Triggers can be set to run manually, based on a condition you set or scheduled. Is there a way to similar functionality in Jira-Server? {{attachment.author.accountId}}: Returnsthe ID associated with the user name. {{issue.comments.first.body}} - Returns the body of the first comment. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. This re-fetches the latest state of the issue from Jira. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. Note that repository contains additional nested smart values. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. There is no Jira smart value referring to approval name (so that we can differentiate when there are multiple approvals in a workflow). For example, you might count how many issues have a . {{branch.repository.name}} returns the name of the repository. Learn more about list smart values. To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. Keep earning points to reach the top of the leaderboard. Smart Commit examples to use with Git and Automation for Jira And we have lots more automation templates and guides for you to use and learn from in the automation template library. They are using the curly-brace syntax like { {someSmartValue}} . This was something we have added since the split and I suspect that the server team has not caught up. You must be a registered user to add a comment. {{comment.created}} - Returns the date and time of the comment. You must be a registered user to add a comment. https://bitbucket.org/account/repo/TEST-123-some-feature. Challenges come and go, but your rewards stay with you. {{issue.affectedServices.tier}} - Returns the tiers of the issue's Affected services. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. That looks a little odd. I've not been able to find such kind of information. for a select field. Added by: Sprint created, started or completed triggers. Understand the general concepts and best practices of automation in Atlassian Cloud products. This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. {{comment.author}} - Returns the ID of comment's author. Learn more about date and time smart values. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). And the rule itself? Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. {{version.description}} - Returns the version's description. The active issue. Access information related to the last branch that was created. Affects version of an issue as a list. Is the IF statement available for Server version? 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. {{attachment.filename}}: Returns the filename of the attachment. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. Also provides the customer portal URL forJira Service Management requests. {{sprint.name}} - Returns the sprint name. issue The active issue. 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. {{versions.releaseDate}}- Returns the affects version's release date. Is the IF statement available for Server version? They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. For example, wheninvalid referencedoesn't contain a value, you can printHello worldusing{{invalid reference|"Hello world"}}. 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. "sd.public.comment".internal}}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Learn more about using smart values with sections and lists. {{issue.InsightField}} - Returns the issue summary and issue key, {{issue.InsightField.key}} - Returns the issue key, {{issue.InsightField.summary}} - Returns the issue summary. {{version.releaseDate}} - Returns the version's release date. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. Here you can access any issue property. Learn more about date smart values. Accesses information fromJira Service Managementrequests. {{changelog.status}} - Changelog information for theStatus field. {{deployment.state}} returns the state of the deployment. https://bitbucket.org/account/repo/TEST-123-some-feature. They allow you to automate tasks and make changes within your site. {{commit.repository.url}} returns the repositorys URL. There is a feature request for it though - check outAUT-648. 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. Added by: Sprint created, started or completed triggers. You can check this by navigating to the "Custom fields" page in the. 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. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). this is only available for some triggers. Please share more details and screenshots in order to be able to help you. 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. it is not supported in server version now. Examples of using smart values with text strings. {{flag.name}} returns the name of the feature flag. Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Refers to the original issue when you branch the chain. 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. Share the love by gifting kudos to your peers. Used with the Related issues condition. Used with: any triggers that edit an issue. For example, if a rule is created that will comment on an issue when executed, the rule actor must have the Add comment permission, otherwise the rule will result in an error. Or you could count how many issues have the same label, same fixVersion, etc. There should be a locked field named either "Request Type" or "Customer Request Type" there. 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. You can also use this withlists. You can view the status of an automation rule to identify if the rule is currently active or not. {{sprint.endDate}} -Returns the end date of the sprint. Understand the general concepts and best practices of automation in Atlassian Cloud products. build#123, {{build.url}} returns the absolute URL of the build, e.g. Smart values are one of the most potent ways to do so. You're on your way to the next level! A pull request represents proposed changes before they are integrated into an official project. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. Automation is a great way to reduce the manual work of keeping story points up to date. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. Learn more about configuring time tracking. Here you can access any issue property. It resets every quarter so you always have a chance! Smart values in Jira automation. Used to access information about an issue's epic. 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. In this case, we want to choose the Field value changed trigger. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. {{issue.created}} - Returns the issue's creation date. Ive tried with both format that you mentioned: Thanks, Sofia. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. Each field is a list of changes. Returns the issue's comments. 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). role. my-awesome-repository. Learn more about user smart values. Or .displayName if accountId doe not work as hoped. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. - theIssue transitionedtrigger). Note that environment contains additional nested smart values. {{pullRequest.createdDate}} returns the time (UTC) when the pull request was created, e.g. {{fieldChange}}only contains the first changed value. If multiple values are changed (e.g. What third-party applications can I integrate with? {{attachment.mimeType}}: Returnsthe file format of the attachment. Share the love by gifting kudos to your peers. Smart values allow you to access issue data within Jira. {{comment.visibility.value}} - Returns the comment restriction label if any, e.g. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. Also provides the customer portal URL for Jira Service Management issues. ^ 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. General triggers These triggers can be used across all Jira products. You can also use this withlists. 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. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. Each field is a list of changes. Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. When we use this trigger, we can use the {{webhookData}} smart value to represent the POST payload - we'll focus on this here. How releases get into the Release Center - Atlassian Community {{issue.project}} - the project this issue is a part of. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. {{addedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to addition of a value. Simply combine these components to create rules that can do anything from auto-closing old issues to notifying specific teams when a release has been shipped. global admin section. Triggers can be set to run on a schedule, and can be customized before being applied to a rule. The status of a rule can be seen on its details screen. {{comment.properties}} - Accesses any comment property. Reviewing your audit logs is an effective way of debugging your rules. Automation rules are made up of three parts: triggers that kick off the rule, conditions that refine the rule, and actions that perform tasks in your site. 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. We select the exact field we are listening out for, in this case story points. 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. Navigate to your project in Jira. See all Jira Cloud automation smart values related to date and time. Join now to unlock these features and more. They allow you to access and manipulate almost any data in Jira. 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. {{issue.latest.description}} - Returns the status's description. 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}}. {{issue.resolution}} - Returns the issue's resolution. {{issue.fixVersions.description}} - Returns the description of the fix version. I recall there are suggestions in the backlog to add "wait until the prior step finishes" or "delay X seconds" actions. Are you looking for server documentation? For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. You can view the audit log of an individual rule, project-wide or at a global level. Connect your source code management, build or deployment tool to use these smart values. Available anywhere smart values are supported, to access the value of a field that has changed. Learn more about user smart values. Create a sample project and follow all of the breadcrumbs in the audit log of the rule details. {{fieldChange.to}}Returns the new raw value, e.g. See all smart values that are used to insert and format numerical values using math expressions. 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! If this issue is in an Epic, then epic refers to the Epic issue. Do you have any idea how I find active sprint smart value? Accesses the values in an issue'sAffected services field. For example, when setting multiple Fix Versions, then you can iterate over these using{{#changelog.fixVersion}}{{toString}}. 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). @Simeon Ross - Any ideas on this one? All of the issues found by the trigger are then treated as a single bundle of issues. For example, you can set up your rule to only escalate an issue if it is high priority. {{version.startDate}} - Returns the version's start date. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. All of the issues found by the trigger are then treated as a single bundle of issues. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. Andit appears you are using Server/Data Center version, as the Re-fetch action does not have the "delay rule" option for Cloud. {{webhookResponse.status}} - response code e.g. {{fieldChange}}only contains the first changed value. {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. [Custom Field]}} - Returns the value in an epic's custom field. 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. Returns the value of the Jira Service Managements scale custom field. PROJ-213, {{issue.epic.status.name}} - Returns the epic's status, e.g. For example,jira:issue_updated :issue_commented. Used with: the Create feature flag in LaunchDarkly action.