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; } } }

Adding Custom Values to Jira Automation

Kinka Family IT

I am trying to crete a automation email to send when a new issue is created, i have a custom field called brands (drop down list with multiple options)

How can i add this custom field to the email automation?

I have tried

Thank you

Accepted answers

Mark Segall

Hi @Kinka Family IT - Please confirm my understanding:

You have a custom multiselect field
You're trying to email the selected values

If this is correct, the smart value syntax would be:

{{issue.customfield_10112.value}}

If multiple values are selected, they would be presented in a comma delimited format (e.g. Option 1, Option 3)

All comments

Valerie Knapp_dpp5c6

Hi @Kinka Family IT , thanks for your question.

Please check here - Jira smart values - issues | Cloud automation Cloud | Atlassian Support

and / or here Find the smart value for a field | Cloud automation Cloud | Atlassian Support

Please can you confirm also that there is a custom field value in the issue you are using to test?

If you can provide the audit log for the rule, this can also help us with the troubleshooting.

Cheers

Kinka Family IT

Hi Valerie

Please see below, I have looked through the links you sent me, tried adding the custom field but still not showing when automating the email

Thank you for your help

Screenshot 2023-07-24 125345.png Screenshot 2023-07-24 125446.png Screenshot 2023-07-24 125656.png

Derek Fields _RightStar_

Is there any value that is being shown where you have referenced {{issue.brands}}? The syntax is correct.

Kinka Family IT

No, as you can see no values are being shown

thank you for your help

Screenshot 2023-07-24 131251.png

Kinka Family IT

These are the values I have tried and the corresponding JSON for reference

${{issue.customfield_0010112}}

${{issue.brands}}

${{customfield_10112.value}}

$ {{issue.fields.customfield_10112.value}}

$ {{brand.value}}

Screenshot 2023-07-24 162512.png

Kinka Family IT

@Mark Segall anychance you know the answer for this? i saw you relied to a few others having the same issue?

Marc -Devoteam-

Hi @Kinka Family IT

Quick and maybe simple questions from my side

Is the Field Brands mandatory on issue creation?
Would you be able to share a screenshot of a created issue?

If all above is correct and an issue has a value for the Brand field.

I would suggest you to add the edit action: Re-fetch issue data, before the action to send the email.

Mark Segall

Hi @Kinka Family IT - Please confirm my understanding:

You have a custom multiselect field
You're trying to email the selected values

If this is correct, the smart value syntax would be:

{{issue.customfield_10112.value}}

If multiple values are selected, they would be presented in a comma delimited format (e.g. Option 1, Option 3)

Kinka Family IT

There is a automated process which chooses the value based on the senders domain name

Here is a screenshot of a issue

thank you for your help

Screenshot 2023-07-25 094233.png

Kinka Family IT

Hi Mark

Thank you for your reply, unfortunately that didn't work

Screenshot 2023-07-25 100511.png Screenshot 2023-07-25 100542.png

Kinka Family IT

I noticed my custom value are not set to a specific project, could this be why they are not showing?

Screenshot 2023-07-25 100731.png

Marc -Devoteam-

So @Kinka Family IT

When the issue get created an automation runs to set the brand, if I'm interpreting you correctly?

To sum-up:

Issue gets created
Issue created
Automation to set the Brand field

So if the brand is set automated, you can only use the value in the field when that field is populated.

The I would suggest to change the automation, to not to be on issue creation. Set an automation on issue updated.

Screenshot 2023-07-25 at 16.22.31.png

Change the Issue Field Condition Components to Brand.

Mark Segall

You'd have issues selecting values if the field context was the problem.

Can you confirm that the field is in fact set during issue creation?

Kinka Family IT

Thank you everyone

I was able to get this working by adding the send email function in the same automation that was adding the branding after performing a re-fetch data

Thank you again for your time and assistance

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management