Hello everyone:
I would like to automate a process in which the Action "Send Email" allows me to send it to a specific adress in a custom field of the issue.
Would it be possible to do it through smart values?
Hello @[deleted]
Thank you for reaching out.
Per your description, I understand you have added a custom field in your Jira project and you need to automatically send a notification to any users added to that custom field upon a specific action. Is that correct?
The Smart value that should be used to configure the Automation rule will depend on the custom field type you are using. That being said, we need the following information to provide you an exact answer:
1- What is the type of the custom field you are using?
2- Can you let us know if you are using a Classic or Next-gen Project?
Supposing you are using a User picker (Multiple Users) custom field in a Classic project, you can properly access the values of this field by using the smart values mentioned in the documentation below:
- Use smart values to access listed values
Giving you a practical example, let's suppose you have a multi-user picker custom field called "My User field". The query below would create a comma-separated list of the user's e-mail addresses in your field:
{{#issue.My User Field}}{{emailAddress}}, {{/}}
Let us know if you have any questions.
Hello Petter
Thanks so much for responding.
The custom field I would use is not a User picker, but a Text field, in which, for example, if I introduce the adress sendmail@example.com, the action Send Email could take this value and proceed with the sending .The project is Classic.
In adittion, I would like to follow the same method in the body of the message with other custom fields. I would like that, if I have the field Name of the product in the issue, the body message varies with the value I have introduced. I understand the method would be the same as the first question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jorge,
I was able to use a custom text field with the following reference format: {{issue.customField_100xx}}
Where 100xx is the identification number of your custom field.
Check your field ID at his URL.
This worked for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@[deleted] Did this work for you? I am trying to do the exact same thing you described and this didn't work for me. My outgoing emails are still failing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using a custom text field as input to the to: address in Automation for Jira.
It is a multi-line text field and works with comma seperated email addresses.
{{issue.customfield_101xx.value}}
Does not work as the smart-value in the to: address.
However
{{customfield_101xx}}
works.
the email addresses needs to be in the format:
user1@example.com, user2@example.com, user3@example.com
not
user1@example.com
user2@example.com
user3@example.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
this is quite the function Im looking for. What is different I want to use the custom field user picker so jira already knows there e-mail addresses.
But it dosent send e-mails to the added users. Do you have any idea what i have to configure more?
Thank you for any input
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How do we insert linked issue keys in the email body while sending emails from Jira automation plugin?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Leads to the issue as viewed in the portal:
If you want the internal link (for Agents) you can just use the smart value {{url}} instead of {{url.customer}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.