It is better to use this than name as it cannot be changed. Learn about the concepts and procedures related to automation in Jira Cloud, Smart values allow you to access issue data within Jira. 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 here) All of the issues found by the trigger are then treated as a single bundle of issues. I would like to use this in a reminder email, that is sent to two people, using as source two different people fields. {{issue.duedate}} - Returns theissue's due date. Can you provide a screenshot of your result? 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. Learn more about list smart values. This smart value accesses the changelog, and a list of changes for each field. {{attachment.author.active}}: Returnstrue if their account is active, andfalse if not. 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). The{{#if }} statement does not seem to work :(, {{issue.issuetype.name}} | {{ #if( eq(issue.issuetype.name, "Task")) }} This is a task {{ / }}. Learn more about using smart values with sections and lists. {{version.releaseDate}} - Returns the version's release date. We do not currently support accessing fields within insight objects. {{issue.watchers.displayName}} - Returns the watcher's display name. {{issue.Customer Request Type}} - Returns the customer request type for older Jira instances. @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 ! {{createdBranches.product}} - returns the products that the branches were created in. Learn more about using smart values with sections and lists. {{versions.releaseDate}}- Returns the affects version's release date. Triggers: Triggers wait for defined events to take place in your Jira instance and will then execute the automation rule. Developers. The comment that triggers the rule is stored in this smart value. when setting multiple Fix Versions) then you can iterate over these using the{{#changelog.fixVersion}}{{toString}}{{/changelog.fixVersion}}expression. Because this smart value deals with multiple items (i.e: issues can have many watchers), it can be used with the#symbol to apply the rule to each individual component. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed. [Custom Field].id}} - Returns the unique id for the field assigned by Jira. The three properties above can also be added to this, for example,{{issue.affectedServices.dependentServices.tier}} will return the dependent services' tiers. They allow you to perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks. Or you could count how many issues have the same label, same fixVersion, etc. Note that this will return an encoded URL; everything after bitbucket.org/ will look different from what you see here. Learn more about list smart values. Seeaccesing multi-value fields.Properties for versions include:name, description, archived, released, releaseDate. When an issue is raised without an assignee, auto-assign to whoever created it. Get answers to your question from experts in the community, Smart value of trigger issue in automation. It resets every quarter so you always have a chance! Possible states include pending, in_progress, successful, failed, cancelled, or unknown. If you've already registered, sign in. Challenges come and go, but your rewards stay with you. The status of a rule can be seen on its details screen. E.g. You can access all fields of the Epic. For example,{{issue.affectedServices.changeApprovers.displayName}} will return their names. {{createdBranches.name}} - returns the names of the branches, {{createdBranches.url}} - returns the URLs of the branches. A list of issues generated by a trigger that runs a JQL search (Incoming Webhooktrigger orScheduledtrigger when set to process in bulk). Accesses information relating to the sprint that triggered the rule. Learn more about using smart values with sections and lists. All properties available to{{issue}}are also available on this smart value. In the example below, we have a custom field calledTeam Leader, and the value of thefield is currentlyAlana Grant. {{issue.Story Points}} - Returns the issue's story point estimate (company-managed Jira Software Cloud only). Seeaccesing multi-value fields, Added by: This is added any time an issue is added. {{addedFieldChanged.fieldId}} - Returns the fieldId of the field that has changed due to addition of a value. {{issue.security.id}} - Returns the security level ID. {{issue.fix.Versions.archived}} - Returns true if the fix version is archived, andfalse if not. The only situation where this is necessary, is where subsequent actions need to have visibility of the latest state of the issue (e.g. Properties are frequently used by add-ons and integrations to store values. Jira smart values in automation rules. Access information related to all branches created in the rule, as a list. Approval completed: accesses information for an approval when an approval step on an issue is accepted or declined. Use an IDE like Visual Studio Code to find the path. {{createdBranch.repository.url}} - returns the repositorys URL. {{addedfieldChange.values}} - Returns the new value/values added. Special conditions and actions are available to create powerful rules that can work across complex issue relationships. If you're not using a Sprint Trigger, I don't believe it's possible to locate the active Sprint via smart values. {{flags.key}} returns the key of the feature flag. Learn more about list smart values. Accesses any issue property. These can be combined with other user smart values. Learn more about date and time smart values. {{issue. See all smart values related to builds, deployments, and source code management. Which Jira-server version supports the use of smart value: "{{#if . }} 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. 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). [property]}}, you can also access custom field information on your issues. {{sprint.name}} - Returns the sprint name. Wonderful :). {{attachment.author.displayName}}: Returnsthe name displayed in your Jira instance. The spacing format is mentioned in the following article: Smart-value-in-published-article-doesn-t-work. {{issue. See all Jira Cloud automation smart values related to date and time. Affects version of an issue as a list. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. {{issue.Story Points estimate}} - Returns the issue's story point estimate (team-managed Jira Software Cloud only). Returns a list of issues from a JQL search caused bythe Lookup issues action. If this issue is a sub-task, then parent refers to the parent issue. These smart values can only be accessed through other root keys (e.g. {{version.id}} - Returns the version's ID. 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). {{fieldChange}}only contains the first changed value. A build represents the process in which files are converted into their final consumable form. Check out how we use smart values in our Jira automation template library. Accesses the value in the issue'sAffects versions field. You can access all fields of the parent. In the dropdown menu, you simply choose the field you want to work on, including custom fields and then edit. 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. Added by: Sprint created, started or completed triggers. This smart-value allows you to access project specific attributes: Jira Service Management specific request type object that you can grab information from. 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}}. They enable customizing automation actions to be useful for your team and your customers. 2 edit issue actions that need to 'add' to the value of a field instead of overwriting it). all fields available to{{issue}}are available here as well. Join the Kudos program to earn points and save your progress. {{changelog.issuetype}} - Changelog information for theIssue type field. ^ 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. See, This allows access to data that was sent along with the incoming webhook, Added by: Send web request with "Wait for response" checked. https://bitbucket.org/account/repo/TEST-123-some-feature. These smart values are only available for the Deployment successful, Deployment failed and Deployment status changed developmenttriggers. 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. {{issue.url.customer}} - Returns the customer portal URL (forJira Service Management requests). PROJ-213, {{issue.epic.status.name}} - Returns the epic's status, e.g. Now whenever the story points of a sub-task changes, it will be reflected in the parent issue. Triggers can be set to run manually, based on a condition you set or scheduled. 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. Accesses the previous issue created in the rule. Looking forward to see it implemented soon! They allow you to access . You can access the current watchers of an issue. Story points are integral for many agile teams. {{flags.name}} returns the name of the feature flag. Hi John, thanks a lot for your quick response.