These smart value functions are for converting issue fields into the JSON format, usually used in advanced field editing and send web request. The following documentation examples are assuming an issue with two versions ("Version 2.0" and "Version 3.0"), a custom single select called Decision with a selected value of "Yes" and a summary titled "Hello World". I got a few steps further. My current automation rule is: When: Issue linked. Types: All link types. Then: Add comment to issue. Comment: { {issue.key}} Comment Visibility: Share with customer. This works great as it comments the link/URL of the linked issue (let's call it "Issue-B"). The problem is, that the comment is also on Issue-B. Working with Text/String. Smart Fields support a number of text manipulation functions. This works with any. 'text' type field such as summary , description, and text custom fields. You can also use text manipulation functions on issue sub-attributes, such as the { {issue.reporter.displayName}}. For example, if you'd like to send out a Slack 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}}. For Cascade Select List field usage, you will need to use the following smart value syntax -. { {issue..value}} - To obtain the parent option value. { {issue..child.value}} - To obtain the child option value. In my example see below -. My custom field is "Country-City". 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 So if you are using team-managed, please change your rules to use this smart value: {{lookupIssues.Story point estimate.sum|0}} And smart values are case-sensitive, so if you are using company-manage, please use this one: {{lookupIssues.Story points.sum|0}} I added a default value of 0 to both to help rule out other problems. Kind regards, Bill How to add form field value to a request type field using smart values. I have a request type that uses the "Summary" field. Attached to this request type is a form. Within this form is a field called "Name of new employee". The "Summary" field on the request type is set hidden and I have added default text to it of: "New Employee Request". DVehU.

jira service management smart values