The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. Added by: Jira Triggers that edit an issue, All the fields that were changed. {{issue.duedate}} - Returns theissue's due date. 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. Smart values in Jira automation | Cloud automation Cloud | Atlassian Jira Automation: Get the Basics Right [2023] - iDalko The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. Share the love by gifting kudos to your peers. Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. They are variables in the sense that their actual values will be calculated while the automation rule is being executed: You can use two types of smart values: Understand the general concepts and best practices of automation in Atlassian Cloud products. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- Which Jira-server version supports the use of smart value: "{{#if . }} global admin section. {{flags.key}} returns the key of the feature flag. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. As ever, test this rule out in your own instance. 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). View topic Examples of using math expression smart values Connect your source code management, build or deployment tool to use these smart values. {{comment.internal}} - forJira Service Management comments, returns false if the comment is visible to customers. If a rule is inactive, it will not execute until it is enabled. There should be a locked field named either "Request Type" or "Customer Request Type" there. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. Every rule starts with a trigger. View topic Find the smart value for a field Learn how to find the right Jira automation smart values for your issue fields in Jira Cloud. It resets every quarter so you always have a chance! Examples of using smart values with text strings. You're on your way to the next level! {{changelog.summary}} - Changelog information for theSummaryfield. Thisshould not be usedsince it requires an expensive reload of issue data. For example, you might count how many issues have a priority of 'highest' and then send an alert. {{version.project.key}} - Returns the project key of the project the version belongs to. This can be obtained by sending a webhook to a webhook test site (like https://requestbin.com) or by intercepting the message by enabling Jira's HTTP access logs and HTTP dump from the System > Logging and Profilingscreen and then checking the request data. Affects version of an issue as a list. Whenever you want to edit a field in Jira, use the 'Edit issue' action. :{{issue.properties.some.value}}. Your smart value must identify a specific attachment for this to work. See all smart values related to builds, deployments, and source code management. 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. Properties are frequently used by add-ons and integrations to store values, e.g. They kick off the execution of your rules. These smart values can only be accessed through other root keys (e.g. Jira smart values - development | Cloud automation Cloud | Atlassian 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. Suggestion re: {{approval}} Smart Value and subfields - Atlassian Reviewing your audit logs is an effective way of debugging your rules. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. I am glad to learn that helped you. {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. This example shows the previous status for issues that are transitioned. Triggers can be set to run manually, based on a condition you set or scheduled. [property]}}, you can also access custom field information on your issues. {{createdBranch.repository.url}} - returns the repositorys URL. All of the issues found by the trigger are then treated as a single bundle of issues. Learn more about automation triggers. Examples of using math expression smart values. If you have multiple webhook responses, you can add the#symbol to apply the rule to each individual response. Thisshould not be usedsince it requires an expensive reload of issue data. Solved: Automation JQL condition: using smart values - Atlassian Community Is there a way to similar functionality in Jira-Server? For example, the smart value{{now.plusDays(5)}} references the current time and adds 5 days to it, while {{issue.summary}} will print off the summary of the issue. {{commit.message}} returns the commit message, e.g. What third-party applications can I integrate with? {{issue.parent.key}} - Returns the issue key of the subtask's parent issue. If multiple values are changed, use # to iterate over these. 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.affectedServices.changeApprovers}} - Returns the account ID of all change approvers of the issue's services. Added by: Sprint created, started or completed triggers. [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. As for if and when the support will go to server, I have no idea. Now whenever this field changes in Jira, this automation rule kicks in. The following example sums all of the story points for issues returned from the JQL search. It resets every quarter so you always have a chance! Whenever you want to edit a field in Jira, use the Edit issue action. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. Properties are frequently used by add-ons and integrations to store values. Used with the Version created, Version updated, and Version released triggers. Learn more about user smart values. After testing, disable both the HTTP dump and access logs to avoid performance issues. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Learn more about date and time smart values. You could then use this to count the number of issues returned. {{issue.components.name}}- Returns the values in the issue'sComponentfield. For example, wheninvalid referencedoesn't contain a value, you can printHello worldusing{{invalid reference|"Hello world"}}. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. {{attachment. It may contain, for example, branches and tags names.This value is optional and may be an empty list. You can also use this with, . 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. I would like the value that enters the text field to be the name of the sprint that created the trigger. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. 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. https://bitbucket.org/{6d6d87be-bdc2-42b5-ad8f-85cb915abc38}/{80c30dd6-2d2f-401c-ac33-8317adbc509d}/addon/pipelines/deployments#!/deployments/{888ba48c-0011-5a46-9d59-8da313851383}. {{issue.security.name}} - Returns the security level name. The status of a rule can be seen on its details screen. General triggers include: Field value changed - when a field value is changed Form submitted - when forms attached to an issue are submitted 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. The trigger for automation is starting a new sprint (trigger = start sprint). {{issue.affectedServices.changeApprovers}}, {{issue.affectedServices.changeApprovers.displayName}}, {{issue.affectedServices.dependentServices}}, {{issue.affectedServices.dependentServices.tier}}, {{issue.Request Type.currentStatus.status}}, {{comment.properties. For example, you can set up your rule to only escalate an issue if it is high priority. 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. The smartvalue{{webhookData}}gets the root of the JSON payload. Used with: the Send web request action (Wait for response enabled). Do more to earn more! This example returns the new value of an issue'sSummary field after it has been changed. 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. Looking forward to see it implemented soon! There is no Jira smart value referring to approval name (so that we can differentiate when there are multiple approvals in a workflow). {{issue.comments.reverse.body}} - Returns the issue's comments, in reverse order. Examples of how you can use smart values to access and format items in a list, such as checkboxes and labels. {addedfieldChange.valueIds}} - Returns the id/ids of new value/values added. These smart values are only available for the Commit created development trigger. Accesses information for the current running rule. There are many ways you can edit a field. {{deletedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to deletion of a value. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. 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? 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). The rule triggers on 'Issue created' and is followed by the 'Send web request' component. Note that repository contains additional nested smart values.