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, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. {{version.project.key}} - Returns the project key of the project the version belongs to. [xxx].size}}: Returnsthe file size of a specific attachment. Used to access the values in an issue'sFix Versionsfield. {{issue.affectedServices.changeApprovers}} - Returns the account ID of all change approvers of the issue's services. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. 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. 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, Examples of using math expression smart values, Examples of using smart values with dates, Examples of using smart values with lists, Examples of using smart values with text strings, 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, Learn how to use these to interact with Jiras REST API. To get a property in it, we should use{{webhookData.someValue.childValue}}. This example returns an issue's previous type, after it has been changed. Or .displayName if accountId doe not work as hoped. Can you provide a screenshot of your result? Learn more about user smart values. {{sprint.originBoardId}} - Returns the ID of the board the sprint belongs to. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. Also provides the customer portal URL for Jira Service Management issues. This value supportsDate and Time functions, e.g. {{fieldChange.from}}- Returns the previous raw value, e.g. Click Create a webhook. What I didn't notice, is that I entered the value: {{issue.sprint.name}}. this is only available for some triggers. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. Navigate to your project in Jira. Used with: Create branch in Bitbucket, Create branch in GitHub, and Create branch in GitLab actions. When we use this trigger, we can use the {{webhookData}} smart value to represent the POST payload - we'll focus on this here. There should be a locked field named either "Request Type" or "Customer Request Type" there. Properties are frequently used by add-ons and integrations to store values, e.g. Now, I want to run automation even without a sprint trigger (scheduled trigger). {{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. 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! This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. We will ensure the story points of the parent and sub-task always remain in sync. {addedfieldChange.field}} - Returns the field which has changed due to addition of a value. Examples of how you can use smart values to manipulate and format dates in your Jira automation rules. Refers to the original issue when you branch the chain. {{issue.comments.first.body}} - Returns the body of the first comment. Note that environment contains additional nested smart values. 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. In this case, we want to choose the Field value changed trigger. In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. 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. Please share more details and screenshots in order to be able to help you. {{versions.archived}}- Returnstrueif the affects version is archived, andfalseif not. issue The active issue. Issue commented, Added by: Clone Issue Action, Create Issue Action, Create Sub-tasks Action, A list of issues that have been created in the rule, The type of event that triggered the rule such as: jira:issue_updated :issue_commented. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. Accesses the values in an issue'sAffected services field. Triggers can be set to run manually, based on a condition you set or scheduled. {{deployment.environment}} returns information related to the deployment environment. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. Send a daily Slack message with a list of issues still open in the Sprint. I'll ask one of their team to update you here. Smart values are variables that you can use in automation action configuration parameters. I created an automation that created a value in a short text field. Learn more about date smart values. You could then use this to count the number of issues returned. I'll mention the docs discrepancies to the person that maintains our documentation. You can check this by navigating to the "Custom fields" page in theglobal admin section. The following example prints all the issue keys returned from the JQL search, in bullet point form. In this case, we want to perform an action on the parent of the sub-task so in the dropdown menu, we choose Parent. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. However, you can now change the rule actor for your automation rules. This example returns the new value of an issue'sSummary field after it has been changed. See all smart values that can access and manipulate text fields, such as issue summary or comments. Connect thousands of apps for all your Atlassian products, Run a world-class agile software organization from discovery to delivery and operations, Enable dev, IT ops, and business teams to deliver great service at high velocity, Empower autonomous teams without losing organizational alignment, Great for startups, from incubator to IPO, Get the right tools for your growing business, Docs and resources to build Atlassian apps, Compliance, privacy, platform roadmap, and more, Stories on culture, tech, teams, and tips, Training and certifications for all skill levels, A forum for connecting, sharing, and learning. You could then use this to count the number of issues returned. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. See all smart values related to builds, deployments, and source code management. They kick off the execution of your rules. [property]}} Returns information related to the created feature flag. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. Can be combined with other date and time smart values. Learn more about date and time smart values. {{issue.comments.size}} - Returns the number of comments on the issue. For example, {{attachment.first.size}} will return the file size of the first attachment. You can also use this withlists. Smart values - syntax and formatting; Jira smart values - issues; Jira smart values - conditional logic; . E.g. {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. Seeaccesing multi-value fields, Added by: This is added any time an issue is added. You can check this by navigating to the "Custom fields" page in the. Smart values allow you to access issue data within Jira. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. It may contain, for example, branches and tags names.This value is optional and may be an empty list. {{comment.author}} - Returns the ID of comment's author. All of the issues found by the trigger are then treated as a single bundle of issues. Automation is currently available in Jira Software Cloud and Confluence Cloud. {{issue.InsightField}} - Returns the issue summary and issue key, {{issue.InsightField.key}} - Returns the issue key, {{issue.InsightField.summary}} - Returns the issue summary. Thank you@Bill Sheboy for answer,The custom field is a Date Picker type. {{version.archived}} - Returnstrue if the version is archived, andfalse if not. {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. You can also use this with, . If you've already registered, sign in. Learn more about list smart values. Automation is a great way to reduce the manual work of keeping story points up to date. {{changelog.status}} - Changelog information for theStatus field. {{deployment.environment}} returns my-custom-prod-env, {{deployment.environment.type}} returns production. 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. Awesome! The smartvalue{{webhookData}}gets the root of the JSON payload. Check out some common DevOps automation rules where you can use these smart values. {{attachment.author.timeZone}}: Returns the timezone the user is registered being in; this doesn't change dynamically based upon where the user logs in from, it is the timeZone registered in their user account. The URL to access the issue. All properties available to{{issue}}are also available on this smart value. This smart value only works for issues that have been added to an epic. The following smart values are available to access and format development information from a connected source code management tool. In this way, approval returns two different values depending on the trigger being Approval required or Approval completed - https://support . Ive tried with both format that you mentioned: Thanks, Sofia. [property]}}, you can also access custom field information on your issues. https://bitbucket.org/account/repo/TEST-123-some-feature. Step 3: Set up the condition like this: Change the field's value to Issue Type. When an issue is raised without an assignee, auto-assign to whoever created it. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. Triggers can be set to run manually, based on a condition you set or scheduled. Returns information related to all feature flags created in throughout the rule or branch, as a list. Is there any information on the web available about the "{{#if functionality)? Join the Kudos program to earn points and save your progress. {{branch.name}} returns the name of the branch, e.g. You can check this by navigating to the "Custom fields" page in the. Also provides the customer portal URL for Jira Service Management issues. Learn more about automation triggers. {{commit.repository}} returns the information related to the repository. It resets every quarter so you always have a chance! {{attachment.author}}: Returnsthe user who added the attachment. That is not the correct custom field id for the field you want. Join the Kudos program to earn points and save your progress. This will return a list of values, if the issue has more than one attachment. Visit the marketplace to integrate your build or deployment tool with Jira Cloud. Your thorough reply here helped me in a completely different use case. This example shows the previous status for issues that are transitioned. 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. This re-fetches the latest state of the issue from Jira. {{deletedFieldChanged.fieldType}} - Returns the fieldType of the field that has changed due to deletion of a value. Now whenever the story points of a sub-task changes, it will be reflected in the parent issue. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components 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. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. Select the Issue fields condition from the New condition drop-down menu. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. We do not currently support accessing fields within insight objects. Looking forward to see it implemented soon! {{issue.created}} - Returns the issue's creation date. {{versions.description}}- Returns the description of the affects version. "sd.public.comment".internal}} -. 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. Smart values allow you to access and manipulate a wide range of issue data within your site. {{attachment.author.emailAddress}}: Returnsthe email address associated with the user name. The URL to access the issue. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. {{issue.fixVersions.name}} - Returns the name of the fix version. 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. 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. For example, when an issue is transitioned you can see what status the issue transitioned from. There are many ways you can edit a field. awesome commit handles everything, {{commit.url}} returns the absolute URL of the commit, e.g. What goes around comes around! 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. Learn more about date and time smart values. Smart values are one of the most potent ways to do so. {{attachment.author.accountId}}: Returnsthe ID associated with the user name. {{issue.description}} - Returns the content in the issue'sDescriptionfield. They must be met for your rule to continue running. 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. {{addedfieldChange.values}} - Returns the new value/values added. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. {{approval}} - Returns the name of the approval. 4877576. You must be a registered user to add a comment. Learn more about configuring time tracking. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. Affects version of an issue as a list. for a select field. You can access all fields of the Epic. It some places it pops up, but there is no real explanation. It resets every quarter so you always have a chance! Similar to{{issue. Here you can access any issue property. This can be almost anything you want. This smart value accesses the changelog, and a list of changes for each field. If a customer has not responded to an issue in 5 days, close the issue and leave a comment. {{sprint.name}} - Returns the sprint name. . The active issue. For more information on when issues is available, see, Multiple comments on the active issue (this example is explained in detail in, Properties for versions include:name, description, archived, released, releaseDate, "Customer Request Type" in older instances of Jira. https://bitbucket.org/account/repo/TEST-123-some-feature. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Affects version of an issue as a list. {{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. Check out how we use smart values in our Jira automation template library. Hi John, thanks a lot for your quick response. Accesses any issue property. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). 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. 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).