Menu
{{sprint.isClosed}} -Returnstrueif the sprint has closed, andfalseif not. Certainly, and I am glad it worked for you! Returns the characters after the amount of characters specified. {{changelog.summary}} - Changelog information for theSummaryfield. If a field or value doesn't exist, it will return an empty value:{{invalid reference}}. {{sprint.endDate}} -Returns the end date of the sprint. They can add significant power and complexity to your rules. For example, if you are sending an HTML email, you may need to encode an issue's description as HTML. Checks to see if the text is not empty, and returns true or false. These smart values are only available for the Pull request created, Pull request declined and Pull request mergedtriggers. The email still returns blank with no values . {{issue.resolution}} - Returns the issue's resolution. If you pair this action with a manual trigger then it makes it really easy to test. Share the love by gifting kudos to your peers. {{addedFieldChange.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. For more information, see:String.indexOf(String). Thanks for your help Watch Like Be the first to like this 464 views Useful when sending Outgoing webhooks as XML. Those HTML list markups were to help when using Lookup so you can produce a list of issues. Learn more about user smart values. Those may help explain what you are observing. Any chance your able to explain the syntax to me; that doesn't look like anything I've seen in the help documentation (& definitely different from what they used in a Jira webinar I just watched). abbreviate (int maxLength) Apologies for the reply to a closed question,
  • {{/}}, https://community.atlassian.com/t5/Automation-questions/lookupIssues-not-returning-any-values/qaq-p/2319022. A deployment represents the process in which a product is released in an environment. This smart value only works for issues that have been added to an epic. If this issue is a sub-task, then parent refers to the parent issue. Get answers to your question from experts in the community, Smart value for linked "relates to" inwardIssue in Jira Automation rule. TEST-123-some-feature, {{branch.url}} returns the URL of the branch, e.g. You can also use this with, . Learn about the concepts and procedures related to automation in Jira Cloud. {{createdBranches.product}} - returns the products that the branches were created in. Learn more about date and time smart values. Trigger is "Issue Updated". All cases are tested in both Text type, Paragraph type, url type. The Atlassian Community can help you and your team get more value out of Atlassian products and practices. For more information, see:String.split(String). Examples of using math expression smart values. Can you help me with phrasing hyper link?? Learn more about using smart values with sections and lists. A branch represents an independent line of development. Similar to{{issue. Available only for the pull request created trigger. 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. Learn more about using smart values with sections and lists. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). These smart values are only available for the Build successful, Build failed and Build status changed developmenttriggers. {{commit.repository}} returns the information related to the repository. We should include support for this in Automation for Jira, such as the examples: Branches to Parent/Child. One other question. Learn more about user smart values, {{approval.completedDate}} - Returns completion date of approval. Learn more about date and time smart values. So this rule works as is if I only have one linked story (like above). 7, {{deployment.url}} returns the absolute URL of the deployment, e.g. {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. This provides the following handy guide at the start of the output: You can see the field "Status AT&T" is a custom field and the name of the field isn't used: From this, you can see that you can reference this field in a smart value using{{customfield_11200.value}}however, you can also substitute customfield_11200 for the field's actual name (which makes it easier to read too){{Status AT&T.value}}. Otherwise, register and sign in. This will return a list of values, if the issue has more than one attachment. You must be a registered user to add a comment. Exclusive to the Approval completed trigger: {{approval.approver}} - Returns approvers account id. I asked about the trigger because if you were using the Issue Linked trigger that would give you access to both issues in the link pair. Can be used in conditional logic. Learn more about using smart values with sections and lists. {{version.releaseDate}} - Returns the version's release date. You could use a Lookup Issues action to retrieve the issues that have the "relates to" link to your trigger issue. What goes around comes around! Returns the characters, from the specified amount of characters, from the left of the text string. For example, I want to set a rule that relates an issue to issue key ID #35. The active issue. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. Returns the number of characters in the text string. TEST-123-some-feature, {{pullRequest.sourceBranch.url}} returns the URL of the source branch, e.g.https://bitbucket.org/account/repo/TEST-123-some-feature. For more information, see:String.replaceAll(String, String). my requirement is it should generate only ATV-237 and should be hyperlinked to its URL. For the vast majority of your use cases, you can simply choose the smart values you need from ouravailable values. {fieldChange.fromString}} - Returns the previous value as displayed. :-)That worked!Again thanks, and have a nice weekend.BR, Matilda. Any way to get around that with this trigger? 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. When setting up an automation, adding the "Link issues" action gives a hint that reads: You can link to the issue that triggered this rule, previously created issue, a smart-value or simply an issue key. For more information, see:String.trim(). I'll await your screen image before offering other guidance that might not be useful. It is better to use this than name as it cannot be changed. On the online community, they serve as thought leaders, product experts, and moderators. iterating over the issue links in the list, Action Code I have to add label with the condition met. I have to dash, but I thought I'd throw this out. Go to the issue that has a value set for the field set and manually trigger the rule - you can then find the results immediately in the audit log. It resets every quarter so you always have a chance! In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. Best practices for optimizing automation rules, View performance insights for automation rules, Connect your automation rule to another tool. https://bitbucket.org/account/repo/TEST-123-some-feature. Learn how to use automation in Confluence Cloud, and see what components and variables you can use to build rules. {{commit.repository.name}} returns the name of the repository, e.g. Fix versions of an issue as a list. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. {{commit.shortHash}} returns the truncated SHA1 hash of the commit, e.g. See all smart values related to user fields, such as Reporter or Assignee. {{attachment.mimeType}}: Returnsthe file format of the attachment. For more information, see:StringUtils. :). Escapes the smart value into a literal text expression that can be used in a regular expression match usingPattern.quote(). 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. This example shows the previous status id (for use in another Edit action). When I remove the <> and use the below syntax I get an email that bullets out the full URL | then the issue key. The changed field value is available anywhere smart values are supported using the{{fieldChange}}substitution. {{sprint.isStarted}} - Returnstrue if the sprint has started, andfalse if not. 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). Use the following URL to view the JSON representation of your issue: Navigate to the field value you want to display in your rule and click on the field. This can be done by iterating over the issue links in the list to build a JSON expression for each. What goes around comes around! Thisshould not be usedsince it requires an expensive reload of issue data. issue in linkedIssues({{triggerIssue.key}},"relates to). Any ideas? {{issue.comments.last.body}} - Returns the body of the last comment. Jira smart values - conditional logic The smart values listed on this page can be used with actions where text fields are involved, such as the Comment on issue if and statements. {{deployment.state}} returns the state of the deployment. 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. Understand the general concepts and best practices of automation in Atlassian Cloud products. Returns the text after the first occurrence of the given separator. Description Currently there is no mention about issue.issuelinks on the Automation for Jira Smart values document. Hi, Trying to make a simple Jira Automation (conditional) rule that (if met) adds a label that contains a smart value of the inward related issueExample. Then copy the dot notation in the footer: In this example, the priority field is selected, which means the smart value is{{issue.fields.priority.name}}however, the fields section is not required so you could just use{{issue.priority.name}}or shorten it further to{{priority.name}}. https://bitbucket.org/account/repo/TEST-123-some-feature. The example below lists each person watching the issue - both their display name and their email address - in bulletpointform. This value won't work for any other trigger, even if a comment was added as a result (e.g. There should be a locked field named either "Request Type" or "Customer Request Type" there. I tried to use the format highlighted in the webinar for the other week, but I cannot get my Issue Key to be hyperlinked. I used some HTML syntax to form the list: You can search the interwebs for generic HTML documentation on building lists like this. Learn more about list smart values. Replaces all literal text matches with a specified replacement. Accesses any issue property. [Custom Field]}} - Returns the value in an epic's custom field. Yeah this certainly should be possible! I want to send a notification with the issues links related to an other issue but I couldnt found the smart value for that. Returns information related to the created feature flag. Share the love by gifting kudos to your peers. Refers to the original issue when you branch the chain. {{rule.name}} - Returns the name of the rule that is currently running. Available anywhere smart values are supported, to access the value of a field that has changed. These smart values are only available for the Commit created development trigger. {{version.released}} - Returnstrue if the version is released, andfalse if not. Challenges come and go, but your rewards stay with you. ISSUE-12: Fix bugs, {{pullRequest.url}} returns the absolute URL of the pull request, e.g.https://bitbucket.org/pull-request/182. Learn more about automation triggers. Firstly, to make your life much easier, you can download an extension to prettify your JSON. HTML encoding is useful for emails and exporting HTML pages. {{issue.comments.reverse.body}} - Returns the issue's comments, in reverse order. For more information, see:StringUtils.leftPad(int, String). [xxx].size}}: Returnsthe file size of a specific attachment. {{issue.fixVersions.released}} - Returnstrue if the fix version is released, andfalseif not. This applies to the legacy Insight app. 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). Learn how to find the right Jira automation smart values for your issue fields in Jira Cloud. {{attachment.author.accountId}}: Returnsthe ID associated with the user name. Developers. is used to add a hyperlink, where href is the URL reference, and the text in the middle is what to show for itin place of the URL. {{issue.affectedServices.changeApprovers}}, {{issue.affectedServices.changeApprovers.displayName}}, {{issue.affectedServices.dependentServices}}, {{issue.affectedServices.dependentServices.tier}}, {{issue.Request Type.currentStatus.status}}, {{comment.properties."sd.public.comment".internal}}. For example, you might count how many issues have a priority of 'highest' and then send an alert. The three properties above can also be added to this, for example,{{issue.affectedServices.dependentServices.tier}} will return the dependent services' tiers. Each field is a list of changes. You can use two types of smart values: The Automation for Jira app comes with a large selection of built-in smart values. Again, the trigger and or condition of the rule doesn't seem to be the issue..and when I have an issue that has only one related linked issue this rule works fine. Join the Kudos program to earn points and save your progress. Useful when sending creating links in emails. In normal smart values, you would use something like {{issue.key}} but if you use {{triggerIssue.key}} then this pulls through the values from the issue which triggered the rule. You can check this by navigating to the "Custom fields" page in the. That may provide some context for the community to offer suggestions. Share the love by gifting kudos to your peers. {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). When we created Automation for Jira, our primary goal was to create a simple, yet powerful app for Jira, that anyone could use. {{issue.watchers.emailAddress}} - Returns the watcher's email address. Performs a regular expression search and returns the first (and only one) matching regular expression group. If multiple values are changed (e.g. {{approval.addedApprovers}} - Returns the set of approvers added to issue. {{attachment.created}}: Returnsthe date and time the attachment was added to the issue. {{createdBranch.repository.url}} - returns the repositorys URL. See all smart values that can manipulate the values of items in a list. {{flag.name}} returns the name of the feature flag. {{attachment. Returns the characters, from the specified amount of characters, from the right of the text string. Challenges come and go, but your rewards stay with you. Learn more about date smart values. Learn more about automation triggers. When you have just one item, no need for them. For example, when setting multiple Fix Versions, then you can iterate over these using{{#changelog.fixVersion}}{{toString}}. My flow is if/then - create issue - link issue. {{issue.assignee.displayName}} - Returns the issue's assignee. 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. New Features: 1 . Or you could count how many issues have the same label, same fixVersion, etc. For more information, see:String.toLowerCase(). I gave you the starting point for the links. {{issue.timetracking.timespent}} - Returns the amount of time that has been logged on the issue in the Time spent field. Here you can access any issue property. However, no matter the first condition you choose for this action, the only options are "trigger issue" and "Most recently created issue". Keep earning points to reach the top of the leaderboard. {{versions.released}}- Returnstrueif the affects version is released, andfalseif not. Some issue properties are more complex, and theyve been described in their own sections on this page. This escapes specific characters to comply with the HTML specifications. Share the love by gifting kudos to your peers. View Json encoding below for details on encoding when sending outgoing webhooks as JSON. In the example below, the issue's first affects version's release date is printed: Accesses the current watchers of an issue. $1 can be used to access a matching group in the replacement. If youre an Automation for Jira app customer on a server product, check out the Automation for Jira documentation for Jira Server. These can be combined with other user smart values. Used to access information about an issue's epic.