When using the Service Desk, I have used user picker custom fields as a way of selecting an individual within a request. This was mainly driven by the need to send automated email updates to the person selected. The issue I have is when using smart values in the automated email text instead of the name of the individual it pulls the unique ID of the user. I was curious if there was a formatting syntax similar to what is used in dates to pull the actual name rather than the unique ID?
I have attached the screenshot of the automated email structure in the automation command as well as the result once it is executed.
Can you try issue.get("customfield_15245")?.displayName
issue.get("customfield_15245") - Is this working?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry can you confirm firstly I have the right structure? I am using it like this -
{{issue.get("customfield_15245")?.displayName}}
You are suggesting I replace it to show this instead -
{{issue.get("customfield_15245")}}
Correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. Actually this issue.get("customfield_15245")?.displayName works for certain groovy scripts. If that doesn't work , you can try {issue.get("customfield_15245")}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have tried {issue.get("customfield_11700")} in automation but in email it is not displaying user name returning same value.
Please find the below screenshot for reference needs to display a user name instead of an email id.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.