Returns a list of issues from a JQL search caused bythe Lookup issues action. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. {{issue.comments.last.body}} - Returns the body of the last comment. 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. Jira smart values in automation rules. Similar to{{issue. {{attachment.mimeType}}: Returnsthe file format of the attachment. 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. @Simeon Ross - Any ideas on this one? 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. {{issue.latest.description}} - Returns the status's description. 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. build#123, {{build.url}} returns the absolute URL of the build, e.g. Properties are frequently used by add-ons and integrations to store values. This will return a list of values, if the issue has more than one attachment. Is there a way to similar functionality in Jira-Server? Connect your source code management, build or deployment tool to use these smart values. The three properties above can also be added to this, for example,{{issue.affectedServices.dependentServices.tier}} will return the dependent services' tiers. Ive tried with both format that you mentioned: Thanks, Sofia. A branch represents an independent line of development. {{issue.parent.Epic Link}} - Returns the issue key of the parent issue's epic. {{version.startDate}} - Returns the version's start date. Which Jira-server version supports the use of smart value: "{{#if . }} You can access the current watchers of an issue. If you have multiple webhook responses, you can add the#symbol to apply the rule to each individual response. Any property used with the{{issue}}smart value can also be used with{{createdIssue}}. Triggers can be set to run manually, based on a condition you set or scheduled. Used with: the Send web request action (Wait for response enabled). 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. As a result of this design, the automation got initiated while triggered by a transition, however the data needed for the automation could not be yet updated. {{commit.message}} returns the commit message, e.g. For Jira Service Management requests only. See all smart values related to builds, deployments, and source code management. Check out how we use smart values in our Jira automation template library. Added by: Webhook TriggerThis allows access to data that was sent along with the incoming webhookThe body of the Webhook request. Or you could count how many issues have the same label, same fixVersion, etc. {{issue.comments.size}} - Returns the number of comments on the issue. When we use this trigger, we can use the {{webhookData}} smart value to represent the POST payload - we'll focus on this here. {{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. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. I've not been able to find such kind of information. {{sprint.isStarted}} - Returnstrue if the sprint has started, andfalse if not. Challenges come and go, but your rewards stay with you. See all smart values that can manipulate the values of items in a list. This example returns the new value of an issue'sSummary field after it has been changed. The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. And we have lots more automation templates and guides for you to use and learn from in the automation template library. Set the Equals condition to true. {{issue.epic. 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). Simply combine these components to create rules that can do anything from auto-closing old issues to notifying specific teams when a release has been shipped. FR Jira Dev Aug 05, 2021 I currently have an Automation workflow that creates multiple tasks and subtasks. Story points are integral for many agile teams. Learn more about user smart values. 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. for a select field. If this issue is a sub-task, then parent refers to the parent 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. {{sprint.name}} - Returns the sprint name. In automation configuration , use "Issue Created" trigger and use the log action to get the smart value below :- 2020-07-20T07:00:00.0+0000. this is only available for some triggers. Send a daily Slack message with a list of issues still open in the Sprint. {{branch.repository.url}} returns the URL, e.g. I would like the value that enters the text field to be the name of the sprint that created the trigger. 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. View topic Examples of using math expression smart values These can be combined with other date and time smart values. This re-fetches the latest state of the issue from Jira. Examples of using smart values with text strings. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. You can check this by navigating to the "Custom fields" page in the. Also provides the customer portal URL forJira Service Management requests. This user must have the relevant permissions to trigger the rule, and complete any actions that may be performed. The active issue. We do not currently support accessing fields within insight objects. They can add significant power and complexity to your rules. 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. Automation is currently available in Jira Software Cloud and Confluence Cloud. Learn more about date and time smart values. There is a feature request for it though - check outAUT-648. This smart value only works for issues that have been added to an epic. {{issue.InsightField}} - Returns the issue summary and issue key, {{issue.InsightField.key}} - Returns the issue key, {{issue.InsightField.summary}} - Returns the issue summary. :{{issue.properties.some.value}}. E.g. An environment represents a distinct ecosystem where products are deployed to. Here you can access any issue property. These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. This example shows the previous status id (for use in another Edit action). {{flag.name}} returns the name of the feature flag. You're on your way to the next level! These smart values are only available for the Commit created development trigger. These smart values are only available for the Branch created development trigger. Smart values in Jira automation. This smart value accesses the changelog, and a list of changes for each field. 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. The problem with the interface was, that it worked in two steps - first the re-open transition and then the update of fields. The "Request Type" prefix may be"Customer Request Type" in older instances of Jira. Smart values allow you to access issue data within Jira. {{createdBranch.repository.url}} - returns the repositorys URL. 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. In progress. Used by triggers that involve adding a comment, such as Issue commented, Issue transitioned, or Issue updated. Can only be used when the active issue is a subtask, and can't be used to access a standard issue's parent issue. {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. The issue is not so much with the smart values itself, but with the {{#if }} statement. You could then use this to count the number of issues returned. This value supportsDate and Time functions. 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. Multiple comments on the active issue (this example is explained in detail inhow to use smart values), Components of an issue as a list. {{deletedFieldChanged.valueIds}} - Returns the id/ids of value/values deleted. . {{pullRequest.title}} returns the title of the pull request, e.g. A deployment represents the process in which a product is released in an environment. {{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). To prevent this, I thought let's use this construct: {{#if(issue.assignee.equals(issue.coordinator))}} Name 1,{{/}}. Again say it aloud: Whenever the field value changes for story points AND it is a sub-taskTHEN for the parent of the sub-task. {{createdBranches.name}} - returns the names of the branches, {{createdBranches.url}} - returns the URLs of the branches. {{branch.repository}}). For example, if the epic has a custom field calledInitiative, then{{issue.epic.Initiative}} will return the value in the Initiative field. 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. {{comment.created}} - Returns the date and time of the comment. Acording with the documentation, Automation JQL condition suport smart values. {{changelog.summary}} - Changelog information for theSummaryfield. There should be a locked field named either "Request Type" or "Customer Request Type" there. : To do,In progress, orDone). This was something we have added since the split and I suspect that the server team has not caught up. What are conditions? What goes around comes around! 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}}. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. Learn more about date and time smart values. {{attachment.filename}}: Returns the filename of the attachment.