Hi
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
{{issue.customfield_10112}}
{{issue.brands}}
Thank you
Hi @Kinka Family IT - Please confirm my understanding:
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)
Hi Mark
Thank you for your reply, unfortunately that didn't work
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I noticed my custom value are not set to a specific project, could this be why they are not showing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nevermind - Just saw one of the other community members ask the question. So the issue is being created and then the field is set by automation after it is created? If that's the case, you may want to change your issue trigger to Field Value Changed. This would mean that the email would go out any time that field is changed, but it would assure that you're not running into automation collisions.
Note - You would also need to check the box in rule details to allow the rule to be triggered by other rules.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Quick and maybe simple questions from my side
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When the issue get created an automation runs to set the brand, if I'm interpreting you correctly?
To sum-up:
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.
Change the Issue Field Condition Components to Brand.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mark Segall anychance you know the answer for this? i saw you relied to a few others having the same issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there any value that is being shown where you have referenced {{issue.brands}}? The syntax is correct.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, as you can see no values are being shown
thank you for your help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
These are the values I have tried and the corresponding JSON for reference
{{issue.url}}
${{issue.customfield_0010112}}
${{issue.brands}}
{{issue.brands.name}}
${{customfield_10112.value}}
$ {{issue.fields.customfield_10112.value}}
{{brands.value}}
{{issue.brands - test.value}}
{{issue.customfield_10112}}
{{issue.customfield_10113}}
{{customfield_10108.value}}
$ {{brand.value}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.