Hi, I have a custom field (Assets Object), where i have different options objects. Now i want to make a simple automation rule where i send the value of this custom field from a ticket into an email. So I have configured automation that says, when a ticket is created on this issue type - send an email: This is a simple rule - and works just fine BUT - being an Assets field - it gets me the value of the field + the ID from the Assets - the result i get on email being: The Impact is: Very High (HOF-8057) How do i get rid of the ID ? i tried {{issue.customfield_11406.name}} - doesn't get me anything. Thanks

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Email Custom field [Assets] trough Automation

Albert Manuel

Hi,

I have a custom field (Assets Object), where i have different options objects. Now i want to make a simple automation rule where i send the value of this custom field from a ticket into an email.

So I have configured automation that says, when a ticket is created on this issue type - send an email:

Screenshot 2023-08-11 182654.png

This is a simple rule - and works just fine BUT - being an Assets field - it gets me the value of the field + the ID from the Assets - the result i get on email being:

The Impact is: Very High (HOF-8057)

How do i get rid of the ID ? i tried {{issue.customfield_11406.name}} - doesn't get me anything.

Thanks

Accepted answers

Albert Manuel

Found the solution - the documentation is a bit wrong or hard to understand.

The solution for those who want to get just the name of the Object and Not the ID, in the server/datacenter editions is to use the formula: {{"Name of your field".summary}} works also with

{{issue.customfield_12345.summary}}

All comments

You are on the right track.

Just use:

{{issue.fields.customfield_11406.label}}
{{issue.fields.customfield_11406.Name}}
{{issue.fields.customfield_11406.AttributName}}

But do note that it is case sensitive. If you use an uppercase in the naming of your attributes in the objectschema, then you need to use it also here.

And 'label' is a special attribute, in the object schema it is mostly used to name your object. But you can have the name attribute called e.g.: Name Nome, Navn, Nom

And with the label you can refer them all as 'label'.

Albert Manuel

Hi Rudy, thanks for jumping in on this.

I have tried all the options with:

{{issue.fields.customfield_11406.label}}
{{issue.fields.customfield_11406.Name}}
{{issue.fields.customfield_11406.My Attribute}}

I have even created my own attribute etc...nothing works - the email it's coming blank where the value of this field should be.... as i said, if i use just {{issue.customfield_11406.name}} works but if i add anything after - it's getting nothing - i need to research more..

Rudy Holtkamp

Could post the JSON of an issue:

https://{yoursite}.atlassian.net/rest/api/latest/issue/{issue}?expand=names

And

A screenshot of the CMDB object you are referring to in that issue?

Albert Manuel

Sure, here is all the information (I'm in datacenter edition):

Here is the JSON - as you can see, there is nothing else:

So i think this is the problem, that even in the Json, there is nothing else...

Albert Manuel

Found the solution - the documentation is a bit wrong or hard to understand.

The solution for those who want to get just the name of the Object and Not the ID, in the server/datacenter editions is to use the formula: {{"Name of your field".summary}} works also with

{{issue.customfield_12345.summary}}

Aaron P_

for me is more easy use the name of the field as appears in the issue, for example:
{{computer.ID}} or {{computer.user}}
but if the field is configured for supports more than one value, you you should use the sintax:
{{#computer}}{{value}}{{/}}
This sintax create a loop and write all values of the field

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server