Hi @Rob. I know this is possible in Slack using smart values, but I haven't tried it with Teams. For Slack, I use smart values such as: { {issue.Time to Resolution.ongoingCycle.goalDuration.friendly}} - time goal of the TTR SLA. { {issue.Time to Resolution.ongoingCycle.elapsedTime.friendly}} - elapsed time of the TTR SLA. To test what your smart value returns, use the manual trigger with log action and the result displays in the audit log.. issue. The active issue. 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) The changed field value is available anywhere smart values are supported using the { {fieldChange}} substitution. 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). { {fieldChange}} only contains the first So we know for sure that we have to focus on the automation configuration. Other than that the first 2 examples you showed should work I think, the "key" one being "probably" the correct way to do it: Assign issue > Smart Value > { {issue.customfield_10926.key}} Assign issue > Smart Value > { {issue.customfield_10926.name}} The way I test it for instance is that I have a service desk request when I need to create a new account for a user. When the request is created , it create 2 sub task attached to the TSD request. using automation I set the description field of the fisrt task by getting the user name using smart value syntax Related smart values: Jira smart values - projects. Rule will run when a project is created. For example, this could be useful if you want to create a set of default issues that should be included in all Jira projects. Scheduled. Related smart values: {{issue}} This rule runs on a specified schedule. QrxBn. 1 answer. Thank you for reaching out. Smart values are only applicable to the Automation rules of Jira, so they can not be used on the customer notification template. In fact, the only variables that can be used in the customer template are the ones suggested in the drop-down, as you mentioned. We have a feature request created to add more 1. {now}.minute - extracts the number of minutes from the current time. 2. .divide (30) produces a fractional amount >0 and <2. 3. .floor returns either 0 or 1. 4. .multiply (30) returns 0 or 30. 5. .withMinute () gets the above result and sets the time to the current time, with minutes set to either :00 or :30. This is a Base64 encoded value for the actual service ID, which you can access from the Services schema with a Service Object insight custom field: Automation doesn't support decoding Base64 values. So you can't look up objects in Insight Services schema based on the Service ID. As a workaround, you can use { {issue.affectedServices.name}}. Smart value { {issue.comments.last.body}} how to format it so URLs in the comments work in an email. We're using the smart value { {issue.comments.last.body}} to show the last comment in the body of an email. If the comment includes links, they show with the Jira link formatting which includes brackets & not something that email programs Raju Mandapaka Jul 14, 2021. Hi Admins, I using look up issue smart value in an automation which shows all issues under an epic with some satisfied conditions and order by some custom field (ASC) Now i would like to pick only 1st issue in that list. Earlier i am using smart value as { {#lookupIssues}} { {key}}, { {/}} -- It gives all issues.

jira service management smart values