You can also use this with, . Learn more about user smart values. 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. {{createdBranches.product}} - returns the products that the branches were created in. You could then use this to count the number of issues returned. They are using the curly-brace syntax like { {someSmartValue}} . For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. {{commit.repository}} returns the information related to the repository. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. Possible states include pending, in_progress, successful, failed, cancelled, or unknown. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. Now whenever this field changes in Jira, this automation rule kicks in. {{flags.key}} returns the key of the feature flag. A representation of a release/version in Jira. 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}}. If a field or value doesn't exist, it will return an empty value:{{invalid reference}}. After testing, disable both the HTTP dump and access logs to avoid performance issues. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. You're on your way to the next level! If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. {{issue. With the 're-fetch issue data' action (which I seldom use), I noticed that this can put the automation execution on-hold for the whole 5 seconds! Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. These smart values can only be accessed through other root keys (e.g{{deployment.environment}}). The rule is running too quickly after the issue is created. . Learn more about using smart values with sections and lists. - theIssue transitionedtrigger). {{branch.repository.url}} returns the URL, e.g. Learn more about list smart values. Used with the Version created, Version updated, and Version released triggers. For smart values related to the Insight feature in Jira Service Management, see Jira smart values - Assets. See all smart values related to Assets in Jira Service Management Cloud. They allow you to access . Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Because this smart value deals with multiple items (i.e: issues can have many watchers), it can be used with the#symbol to apply the rule to each individual component. Accesses information related to a file attachment on an issue. You can access all fields of the parent. You can also use the quick search (keyboard shortcut is . Do more to earn more! {{comment.visibility.type}} - Returns the comment restriction type if any, e.g. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. {{changelog.summary}} - Changelog information for theSummaryfield. Share the love by gifting kudos to your peers. I would like the value that enters the text field to be the name of the sprint that created the trigger. - Any ideas on this one? In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. What goes around comes around! [property]}}, you can also access custom field information on your issues. They enable customizing automation actions to be useful for your team and your customers. 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. This value supports Date and Time functions. {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. What are conditions? Because this smart value deals with multiple items (i.e: issues usually have many comments), it can be used with the # symbol to apply the rule to each individual comment. ^ 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. 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. These smart values are only available for the Branch created development trigger. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. This value supportsDate and Time functions. You're on your way to the next level! This was something we have added since the split and I suspect that the server team has not caught up. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. In this case, we want to choose the Field value changed trigger. If multiple values are changed (e.g. {{versions.archived}}- Returnstrueif the affects version is archived, andfalseif not. Accesses the previous issue created in the rule. {{comment.created}} - Returns the date and time of the comment. Accesses information relating to the sprint that triggered the rule. {{version.name}} - Returns the version's name. {{issue. {{commit.repository.url}} returns the repositorys URL. {{build.name}} returns the name of the build, e.g. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. {{createdBranch.repository.url}} - returns the repositorys URL. To test what your smart value returns, use themanual triggerwithlog actionand the result displays in theaudit log. Approval completed: accesses information for an approval when an approval step on an issue is accepted or declined. Use{{fieldChange.fromString}}and{{fieldChange.toString}}to access display values and{{fieldChange.from}}and{{fieldChange.to}}to access raw values (for a select field for example). {{fieldChange.from}}- Returns the previous raw value, e.g. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. {{deployment.environment}} returns information related to the deployment environment. Approval required: accesses information when an issue that requires approval is created or updated, or when new approvers are added to 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). {{issue.epic. The URL to access the issue. {{fieldChange}}only contains the first changed value. Navigate to your project in Jira. You can access all fields of the Epic. {{addedfieldChange.values}} - Returns the new value/values added. Or .displayName if accountId doe not work as hoped. Learn more about using smart values with sections and lists. There should be a locked field named either "Request Type" or "Customer Request Type" there. Note that repository contains additional nested smart values. 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. Keep earning points to reach the top of the leaderboard. 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. 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. Similar to{{issue. What goes around comes around! Which Jira-server version supports the use of smart value: "{{#if }} text {{/}}, or is this a Jira-cloud only functionality ? All of the issues found by the trigger are then treated as a single bundle of issues. Access information related to the last branch that was created. There should be a locked field named either "Request Type" or "Customer Request Type" there. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. {{versions.description}}- Returns the description of the affects version. 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. 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.). Affects version of an issue as a list. What third-party applications can I integrate with? Smart values are one of the most potent ways to do so. What goes around comes around! Issues in Jira rarely exist in isolation. Here, we choose the Issue fields' condition and clarify that the issue type we are looking out for is a sub-task. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. Examples of using smart values with text strings. 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! See all Jira Cloud automation smart values related to date and time. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{attachment.author.accountId}}: Returnsthe ID associated with the user name. Properties are frequently used by add-ons and integrations to store values. Affects version of an issue as a list. 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). {{comment.author}} - Returns the ID of comment's author. However sometimes the two fields holds the same person, resulting in an email with twice the same name. Challenges come and go, but your rewards stay with you. {{attachment.author}}: Returnsthe user who added the attachment. Learn how to find the right Jira automation smart values for your issue fields in Jira Cloud. Now whenever the story points of a sub-task changes, it will be reflected in the parent issue. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. If multiple values are changed (e.g. Learn about the concepts and procedures related to automation in Jira Cloud. Accesses the value in the issue'sAffects versions field. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. Learn more about configuring time tracking. 2020-07-20T07:00:00.0+0000. {{issue.duedate}} - Returns theissue's due date. If this issue is a sub-task, then parent refers to the parent issue. See all smart values that can access and manipulate text fields, such as issue summary or comments. For example, checking that all sub-tasks of a parent issue are resolved. Available only for the pull request created trigger. {{issue.url}} - Returns the URL of the issue. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Refers to the original issue when you branch the chain. There should be a locked field named either "Request Type" or "Customer Request Type" there. Share the love by gifting kudos to your peers. This is a list of metadata that can be associated with a build. This re-fetches the latest state of the issue from Jira. Learn more about working with related issues. "sd.public.comment".internal}}, Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . Can be combined with other date smart values. Just for future visibility (for anyone else who finds this question), I tested a few of the options in the linked question above, and another question which was linked to from there. {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. Learn more about using smart values with sections and lists. There is a feature request for it though - check outAUT-648. Access information related to all branches created in the rule, as a list. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. {{issue.created}} - Returns the issue's creation date. We will ensure the story points of the parent and sub-task always remain in sync. I've not been able to find such kind of information. If a condition fails, the rule will stop running and no actions following the condition will be performed. Fix versions of an issue as a list. {{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). Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. These smart values can only be accessed through other root keys (e.g. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. {{branch.name}} returns the name of the branch, e.g. {{changelog.status}} - Changelog information for theStatus field. Returns the value of the Jira Service Managements scale custom field. {{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue. {{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. {{issue.watchers.emailAddress}} - Returns the watcher's email address. Possible states are production, staging, testing, development, and unknown, Used with: the Sprint created, Sprint started and Sprint completed triggers. 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. You can access the current watchers of an issue. {{version.id}} - Returns the version's ID. Join now to unlock these features and more. Platform Notice: Cloud, Server, and Data Center - This article applies equally to all platforms. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. {{commit.hash}} returns the SHA1 hash of the commit, e.g.4877576951f3eda43625d3345058e702dad3df0d. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. E.g. 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. Or you could count how many issues have the same label, same fixVersion, etc. This applies to the legacy Insight app. In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. Examples of using math expression smart values. For Jira Service Management requests only. The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. Reviewing your audit logs is an effective way of debugging your rules. For example, {{attachment.first.size}} will return the file size of the first attachment. This example shows the previous status for issues that are transitioned. {{issue.assignee.displayName}} - Returns the issue's assignee. The trigger for automation is starting a new sprint (trigger = start sprint). You can access all fields of the Epic. Accesses information for the current running rule. I'll mention the docs discrepancies to the person that maintains our documentation. Used with: the Create feature flag in LaunchDarkly action. Learn about the concepts and procedures related to automation in Jira Cloud. 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) This smart value only works for issues that have been added to an epic. A branch represents an independent line of development. For more information on when issues is available, seeRun a rule against issues in bulk. [Custom Field].defaultValue}} - Returns the value displayed on first view of the field. {{version.project.key}} - Returns the project key of the project the version belongs to. 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. Get answers to your question from experts in the community, Automation JQL condition: using smart values. We select the exact field we are listening out for, in this case story points. Whenever you want to edit a field in Jira, use the 'Edit issue' action. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Click Create a webhook. {{pullRequest.destinationBranch.repository}} returns information related to the destination branchs repository. You could then use this to count the number of issues returned. Learn more about automation triggers. @Simeon Ross - Any ideas on this one? Learn more about date and time smart values. Would be good and useful functionality to have. A commit represents an individual change to a file (or set of files). 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. Learn more about user smart values. OMGYou're right. {fieldChange.toString}}- Returns the new value as displayed. You could then use this to count the number of issues returned. A pull request represents proposed changes before they are integrated into an official project. Hi John, thanks a lot for your quick response. https://bitbucket.org/account/repo. role. 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. And we have lots more automation templates and guides for you to use and learn from in the automation template library. Share the love by gifting kudos to your peers. I created an automation that created a value in a short text field. Do you have any idea how I find active sprint smart value? {{version.startDate}} - Returns the version's start date. 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. 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. {{issue.resolution}} - Returns the issue's resolution. {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. The URL to access the issue. Learn more about using smart values with sections and lists. Can be combined with other date and time smart values. {{versions.releaseDate}}- Returns the affects version's release date. When an epic is marked as done move all of its stories to done also. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{changelog.issuetype}} - Changelog information for theIssue type field. {{issue.description}} - Returns the content in the issue'sDescriptionfield. 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. Thisshould not be usedsince it requires an expensive reload of issue data. [Custom Field].name}} - Returns the visible label displayed on the left of the field. Fix versions of an issue as a list. Note that environment contains additional nested smart values. The active issue. it is not supported in server version now. {{comment.properties. Summary Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. Used to access information about an issue's epic. {{comment.body}} - Returns the body of the comment that triggered the rule. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. Or you could count how many issues have the same label, same fixVersion, etc. Added by: Jira Triggers that edit an issue, All the fields that were changed. ), then type 'webhooks'. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. Go to Jira administration console > System > Webhooks (in the Advanced section). 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. If a rule is inactive, it will not execute until it is enabled. Can you provide a screenshot of your result? Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here.