They allow you to automate tasks and make changes within your site. {{issue.affectedServices.name}} - Returns the names of the issue's Affected services. These smart values are only available for the Branch created development trigger. Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. This value supportsDate and Time functions, e.g. {{issue.reporter.displayName}} - Returns the issue's reporter. 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. this is only available for some triggers. Connect your source code management, build or deployment tool to use these smart values. Jira smart values in automation rules. Now, I want to run automation even without a sprint trigger (scheduled trigger). Solved: Smart value of trigger issue in automation Can be used with both Approval required and Approval completed triggers: {{approval.createdDate}} - Returns creation date of approval. 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. And we have lots more automation templates and guides for you to use and learn from in the automation template library. Triggers: Triggers wait for defined events to take place in your Jira instance and will then execute the automation rule. 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. {{branch.repository.url}} returns the URL, e.g. {{issue. {{environment.name}} returns the use-provided name for the environment, e.g. This will return a list of values, if the issue has more than one attachment. Examples of using smart values with dates. Jira automation triggers | Automation for Jira Data Center - Atlassian 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. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. Share the love by gifting kudos to your peers. {{deletedFieldChanged.values}} - Returns the value/values deleted. Go to Jira administration console > System > Webhooks (in the Advanced section). { {issue. As ever, test this rule out in your own instance. {{createdBranch.repository}} - accesses details of the branchs repository, {{createdBranch.repository.id}} - returns the repositorys ID, {{createdBranch.repository.name}} - returns the repositorys name. A commit represents an individual change to a file (or set of files). Learn more about user smart values. You could then use this to count the number of issues returned. For example, you might count how many issues have a priority of 'highest' and then send an alert. Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. {{issue.components.name}}- Returns the values in the issue'sComponentfield. . {{issue.description}} - Returns the content in the issue'sDescriptionfield. See all smart values related to builds, deployments, and source code management. Can be combined with other date and time 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. [property]}}, you can also access custom field information on your issues. Learn about the concepts and procedures related to automation in Jira Cloud. Here you can access any issue property. [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. Step 2: Save the Issue generated trigger. We do not currently support accessing fields within insight objects. Access information related to the last branch that was created. Otherwise, register and sign in. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. {{pullRequest.title}} returns the title of the pull request, e.g. Jira Automation: Building New Rules in 5 Easy Steps - Hevo Data This applies to the legacy Insight app. What third-party applications can I integrate with? Learn about the concepts and procedures related to automation in Jira Cloud. role. ^ 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. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. text {{/}}, or is this a Jira-cloud only functionality ? Your thorough reply here helped me in a completely different use case. {{deletedFieldChanged.field}} - Returns the field that value has changed due to deletion of a value. Can be combined with other user smart values. Accesses information relating to the sprint that triggered the rule. In progress. You can check this by navigating to the "Custom fields" page in theglobal admin section. You could then use this to count the number of issues returned. @Simeon Ross - Any ideas on this one? {{build.refs}} returns the refs of the build, e.g. A representation of a release/version in Jira. Learn more about list smart values. This example returns an issue's previous type, after it has been changed. Do more to earn more! Note that environment contains additional nested smart values. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. twoEdit issueactions that need toaddto the value of a field, instead of overwriting it. Your image appears to show too many curly-brackets around the value. For example, you might count how many issues have a . PROJ-213, {{issue.epic.status.name}} - Returns the epic's status, e.g. 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 . Possible states include pending, in_progress, successful, failed, cancelled, or unknown. I would like the value that enters the text field to be the name of the sprint that created the trigger. A selection of smart values make Jira issue details readily available for Automation for Jira rules. {{issue.affectedServices.tier}} - Returns the tiers of the issue's Affected services. {{createdBranch.product}} - returns the product that the branch was created in (for example, Bitbucket). What third-party applications can I integrate with? 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. Approval required: accesses information when an issue that requires approval is created or updated, or when new approvers are added to an issue. When there are multiple fields that have changed, {{fieldChange}}only contains the first changed value. It is better to use this than name as it cannot be changed. You can access useful things like the previous status during a transition, Added by: Jira Triggers that contain a comment. Whenever you want to edit a field in Jira, use the 'Edit issue' action. 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). Learn more about using smart values with sections and lists. @Daniel Ramotowski, more people seem to be interested in this functionality, as there was already a ticket open forhttps://jira.atlassian.com/browse/JIRAAUTOSERVER-212 ! The rule triggers on 'Issue created' and is followed by the 'Send web request' component. Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. Can be combined with other date and time smart values. Jira Automation: Get the Basics Right [2023] - iDalko See all smart values that take issue fields and convert them into JSON format. {{version.id}} - Returns the version's ID. Join the Kudos program to earn points and save your progress. {{issue.affectedServices.dependentServices}}- Returns the list of services that this issue's services depend on. General triggers include: Field value changed - when a field value is changed Form submitted - when forms attached to an issue are submitted 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. {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. The smartvalue{{webhookData}}gets the root of the JSON payload. Summary Automation for Jira has a trigger that reads incoming webhooks, both in on-premises and cloud intances. {{attachment.created}}: Returnsthe date and time the attachment was added to the issue. {{commit.repository}} returns the information related to the repository. Which Jira-server version supports the use of smart value: "{{#if . }} Learn more about using smart values with sections and lists. {{issue.comments.last.body}} - Returns the body of the last comment. Any idea if this will be added, and if so when? {{pullRequest.destinationBranch.repository}} returns information related to the destination branchs repository. Is the IF statement available for Server version? The Atlassian Community can help you and your team get more value out of Atlassian products and practices. We use the following smart-value to sum up story points from all sub-tasks: {{issue.subtasks.Story Points.sum}}. {{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. If this issue is a sub-task, then parent refers to the parent issue. Smart values allow you to access and manipulate a wide range of issue data within your site. Accesses any issue property. If this issue is in an Epic, then epic refers to the Epic issue. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. Syntax example The smartvalue { {webhookData}} gets the root of the JSON payload. {{issue.security.id}} - Returns the security level ID. Acording with the documentation, Automation JQL condition suport smart values. {{issue.watchers.displayName}} - Returns the watcher's display name. {{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. Returns the issue's comments. If multiple values are changed (e.g. Accesses the previous issue created in the rule. You're on your way to the next level! Here, we choose the Issue fields' condition and clarify that the issue type we are looking out for is a sub-task. {{addedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to addition of a value. Or you could count how many issues have the same label, same fixVersion, etc. {{comment.properties}} - Accesses any comment property. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. See all smart values that can manipulate the values of items in a list. See all smart values related to Assets in Jira Service Management Cloud. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. If youre an Automation for Jira app customer on a server product, check out the Automation for Jira documentation for Jira Server. If a customer has not responded to an issue in 5 days, close the issue and leave a comment. 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. Jira smart values - issues | Automation for Jira Data Center and Server {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). {{issue.epic. {{issue.latest.description}} - Returns the status's description. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). You can access all fields of the parent. Is the IF statement available for Server version? {{flag.key}} returns the key of the feature flag. Step 4: Add 'Edit Issue' action . Solved: Automation JQL condition: using smart values - Atlassian Community 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. {{issue.parent.priority.name}} - Returns the priority of the subtasks's parent issue. Added by: Sprint created, started or completed triggers. You can access the current watchers of an issue. Challenges come and go, but your rewards stay with you. This value supports Date and Time functions. Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . Used with: the Send web request action (Wait for response enabled). {{issue. We will ensure the story points of the parent and sub-task always remain in sync. Check out some common DevOps automation rules where you can use these smart values. 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. The following example sums all of the story points for issues returned from the JQL search. All of the issues found by the trigger are then treated as a single bundle of issues. Learn more about using smart values with sections and lists. Understand the general concepts and best practices of automation in Atlassian Cloud products. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. [Custom Field]}} - Returns the value in an epic's custom field. Returns information related to all feature flags created in throughout the rule or branch, as a list. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. Fix versions of an issue as a list. {{sprint.startDate}} - Returns the start date of the sprint. TEST-123-some-feature, {{branch.url}} returns the URL of the branch, e.g. {{issue.url}} - Returns the URL of the issue. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. You can also use this with, . {{issue.updated}} - Returns the date the issue was updated. Possible states include pending, in_progress, successful, failed, cancelled, rolled_back, or unknown. 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. Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. 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! {{commit.shortHash}} returns the truncated SHA1 hash of the commit, e.g. They are using the curly-brace syntax like { {someSmartValue}} . I recall there are suggestions in the backlog to add "wait until the prior step finishes" or "delay X seconds" actions. Wonderful :). Examples of how you can use smart values to set the text value of an issues field, such as Summary or Description. All of the issues found by the trigger are then treated as a single bundle of issues. Click Create a webhook. ISSUE-12: Fix bugs, {{pullRequest.url}} returns the absolute URL of the pull request, e.g.https://bitbucket.org/pull-request/182. General triggers These triggers can be used across all Jira products. Webhooks - Atlassian When a PR is merged in Bitbucket/GitHub/GitLab, then transition the issue in Jira. In the project menu, click on Project Settings. I created an automation that created a value in a short text field. 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). This is a list of metadata that can be associated with a build. {{issue.parent.epic.summary}} - Returns the summary of the parent issue's epic. {{fieldChange}}only contains the first changed value. In the form that is shown, enter the details for your new webhook. The URL to access the issue. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. Understand the general concepts and best practices of automation in Atlassian Cloud products. If you've already registered, sign in. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. Find issues that have the same custom field date as trigger issue. {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. This example shows the previous status for issues that are transitioned. Used with: the Create feature flag in LaunchDarkly action. You can also use this withlists. 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. There should be a locked field named either "Request Type" or "Customer Request Type" there. this is only available for some triggers. Do more to earn more! Learn more about list smart values. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. A build represents the process in which files are converted into their final consumable form. For example, you might count how many issues have a priority of 'highest' and then send an alert. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. Ive tried with both format that you mentioned: Thanks, Sofia. Get answers to your question from experts in the community, Automation JQL condition: using smart values. They can add significant power and complexity to your rules. You could then use this to count the number of issues returned. 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. {{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. The information that you can access on the issue are described in the Available properties section below. It resets every quarter so you always have a chance! If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. Is there a way to similar functionality in Jira-Server? Exclusive to the Approval required trigger: {{approval.initiator}} - Returns account id of initiator of request. {{attachment. A repository represents a collection of files and associated metadata. Jira smart values - issues | Automation for Jira Data Center and Server Each field is a list of changes. For example, when an issue is transitioned you can see what status the issue transitioned from. The three properties above can also be added to this, for example,{{issue.affectedServices.dependentServices.tier}} will return the dependent services' tiers. You can set triggers to run on a schedule or as needed. Your smart value must identify a specific attachment for this to work. {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. It resets every quarter so you always have a chance! If this issue is in an Epic, then epic refers to the Epic 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. A pull request represents proposed changes before they are integrated into an official project. 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. {fieldChange.fromString}} - Returns the previous value as displayed. A condition refines the rule so it wont act too broadly.