Awesome! Is there any information on the web available about the "{{#if functionality)? View the list of available triggers. You're on your way to the next level! {{attachment.created}}: Returnsthe date and time the attachment was added to the issue. The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. {{createdBranches.product}} - returns the products that the branches were created in. You were right, the rule was running too quickly, so the field was empty.I modify de trigger to give it time, and got the result expected. [Custom Field].id}} - Returns the unique id for the field assigned by Jira. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. For Jira Service Management requests only. Or you could count how many issues have the same label, same fixVersion, etc. These can be combined with other date and time smart values. It resets every quarter so you always have a chance! Returns the value of the Jira Service Managements scale custom field. These smart values are only available for the Branch created development trigger. Check out how we use smart values in our Jira automation template library. E.g. Smart values allow you to access issue data within Jira. Click Create a webhook. Because this smart value deals with multiple items (i.e: issues can have many Affects versions), it can be used with the#symbol to apply the rule to each individual component. Is there a way to similar functionality in Jira-Server? Returns information related to the created feature flag. 4877576. Which Jira-server version supports the use of smart value: "{{#if }} text {{/}}, or is this a Jira-cloud only functionality ? However, you can now change the rule actor for your automation rules. Find issues that have the same custom field date as trigger issue. The rule actor is the user who executes a rule. What are conditions? It is better to use this than name as it cannot be changed. Learn more about date and time smart values. https://bitbucket.org/account/repo. [Custom Field].defaultValue}} - Returns the value displayed on first view of the field. Affects version of an issue as a list. The issue smart values are used to access information related to the rules active issue, which is the issue the rule is currently acting on. {{comment.created}} - Returns the date and time of the comment. The status of a rule can be seen on its details screen. {{deletedFieldChanged.values}} - Returns the value/values deleted. They allow you to access . If a rule is inactive, it will not execute until it is enabled. {{deployment.state}} returns the state of the deployment. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. You can view the status of an automation rule to identify if the rule is currently active or not. In this template, we show you how to sum up the story points of all sub-tasks then update the parent issue with this value. Step 1: In the top-right corner of your Jira Automation Settings, select Create Rule. You can access all fields of the Epic. They are using the curly-brace syntax like { {someSmartValue}} . {{issue.parent.epic.summary}} - Returns the summary of the parent issue's epic. {{attachment.filename}}: Returns the filename of the attachment. {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. Hi John, thanks a lot for your quick response. The active issue. On successful request, you will be able access webhook response data using the following smart values: The worklog entry that has just been logged against an issue. {{comment.properties}} - Accesses any comment property. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. {{sprint.name}} - Returns the sprint name. Accesses information related to a file attachment on an issue. 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. {{version.project.key}} - Returns the project key of the project the version belongs to. 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. Returns a list of issues from a JQL search caused bythe Lookup issues action. Or .displayName if accountId doe not work as hoped. When there are multiple fields that have changed, {{fieldChange}}only contains the first changed value. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. {{comment.body}} - Returns the body of the comment that triggered the rule. If a customer has not responded to an issue in 5 days, close the issue and leave a comment. You must be a registered user to add a comment. Learn more about using smart values with sections and lists. Learn about the concepts and procedures related to automation in Jira Cloud. The trigger for automation is starting a new sprint (trigger = start sprint). it is not supported in server version now. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. Learn more about automation triggers. You can also use this withlists. 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). @Simeon Ross - Any ideas on this one? You can find some automation templates to help you get started within the product library. Please raise suggestion ticket in our public tracker, https://jira.atlassian.com/projects/JIRAAUTOSERVER. {{version.id}} - Returns the version's ID. What third-party applications can I integrate with? In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- {{attachment.mimeType}}: Returnsthe file format of the attachment. At the same time, it would be to good to mention that it is Jira-cloud functionality only. Used with the Version created, Version updated, and Version released triggers. Fix versions of an issue as a list. For example, you might count how many issues have a priority of 'highest' and then send an alert. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. {{issue.comments.size}} - Returns the number of comments on the issue. If you've already registered, sign in. Automation is a great way to reduce the manual work of keeping story points up to date. This value won't work for any other trigger, even if a comment was added as a result (e.g. You can specify a default value to prevent this. {{issue.comments.author.displayName}} - Returns the comment authors. {{createdBranch.name}} - returns the name of the branch, {{createdBranch.url}} - returns the URL of the branch. {{branch.name}} returns the name of the branch, e.g. Instead using Re-fetch for Cloud slows the rule for about 1 second (or more). When an epic is marked as done move all of its stories to done also. Allows access to data that was sent along with the incoming webhook, for example, the body of the webhook request. 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. {{changelog.summary}} - Changelog information for theSummaryfield. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. {{pullRequest.updatedDate}} returns the time (UTC) when the pull request was last updated (created, declined or merged), e.g. Actions are the doers of your rule. Developers. They can add significant power and complexity to your rules. Note that repository contains additional nested smart values. Every rule starts with a trigger. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. Used by triggers that involve adding a comment, such as Issue commented, Issue transitioned, or Issue updated. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. "sd.public.comment".internal}} -. Your image appears to show too many curly-brackets around the value. {{branch.repository.url}} returns the URL, e.g. This example shows the previous status id (for use in another Edit action). Any idea if this will be added, and if so when? General triggers These triggers can be used across all Jira products. 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. Otherwise, register and sign in. For example, {{attachment.first.size}} will return the file size of the first attachment. {{createdBranch.repository.url}} - returns the repositorys URL. {{addedfieldChange.values}} - Returns the new value/values added. 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. {{issue.affectedServices.dependentServices}}- Returns the list of services that this issue's services depend on. Learn more about using smart values with sections and lists. {{rule.name}} - Returns the name of the rule that is currently running. [property]}}, you can also access custom field information on your issues. A condition refines the rule so it wont act too broadly. {{issue.Request Type.currentStatus.status}} - Returns the status of the current request. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. For example,jira:issue_updated :issue_commented. These smart values are only available for the Build successful, Build failed and Build status changed development triggers. This will return a list of values, if the issue has more than one attachment. {{issue. Acording with the documentation, Automation JQL condition suport smart values. Learn more about user smart values. Jira automation - Data Center and Server (Latest), Examples of using smart values with dates, Examples of using smart values with lists, Examples of using math expression smart values, Examples of using smart values with text strings. This example returns the new value of an issue'sSummary field after it has been changed. 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. Learn more about working with related issues. Learn more about date and time smart values. To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. Get answers to your question from experts in the community, Smart value of trigger issue in automation. Jira smart values - JSON functions See all smart values that take issue fields and convert them into JSON format. Learn more about using smart values with sections and lists. . 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. {{pullRequest.state}} returns the state the pull request is in - Open, Merged, or Declined. Returns the value of the Jira Service Managements scale custom field. Send a daily Slack message with a list of issues still open in the Sprint. If you've already registered, sign in. [feature/ISSUE-123-some-work, feature/ISSUE-456-more-work]. {{deployment.environment}} returns information related to the deployment environment. Examples of how you can use smart values to set the numerical value of an issues field in your Jira automation rules. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. When we use this trigger, we can use the { {webhookData}} smart value to represent the POST payload - we'll focus on this here. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). We do not currently support accessing fields within insight objects. Note that environment contains additional nested smart values. You could then use this to count the number of issues returned. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. Examples of using smart values with lists. {{branch.repository}}). The legacy Insight App will reach end of service on March 31, 2022. {{attachment. Learn more about user smart values. {{issue.updated}} - Returns the date the issue was updated. Learn more about using smart values with sections and lists. "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 user smart values. First, you need a sample from the webhook payload data. 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. For more information on this, see Configuring a webhook later on this page. Thanks for sharing the link back in this question, it might help others in future! 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. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. {{pullRequest.sourceBranch}} returns information related to the source branch for the pull request. 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. 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. {{issue.issueType.name}} -Returns the issue's type, for exampleStory,Bug, orTask. 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. {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). Challenges come and go, but your rewards stay with you. 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. Now, I want to run automation even without a sprint trigger (scheduled trigger). The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. Otherwise, register and sign in. Added by: Sprint created, started or completed triggers. 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. Story points are integral for many agile teams. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. For example, PROJ-123. 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. In the below example, we're sending out a notification that someone has added a comment to an issue, perhaps as a Slack message.