Email this issue - Using custom fields as recipients

[Jonathan Porta]

Hi, 

I'm trying to use a specific custom field to list the recipients of the post-action i've setup.

My custom field is of type labels, and this kind of configuration works in Jira automation. 

Here I get a failed execution with a "No recipient" error and a java call stack:

java.util.concurrent.ExecutionException: com.metainf.connect.jira.jeti.email.NoRecipientsException: No recipients at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at com.metainf.connect.jira.jeti.service.outgoing.OutgoingMailQueue$MailQueueExecutor.afterExecute(OutgoingMailQueue.java:282) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750) Caused by: com.metainf.connect.jira.jeti.email.NoRecipientsException: No recipients at com.metainf.connect.jira.jeti.email.EmailBuilderImpl.resolveRecipients(EmailBuilderImpl.java:295) at com.metainf.connect.jira.jeti.email.EmailBuilderImpl.buildEmailLocally(EmailBuilderImpl.java:167) at com.metainf.connect.jira.jeti.email.EmailBuilderImpl.buildAndSendEmail(EmailBuilderImpl.java:135) at com.metainf.connect.jira.jeti.service.outgoing.OutgoingMailQueueItem.run(OutgoingMailQueueItem.java:56) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ... 2 more

[Gor Greyan]

Hi @Jonathan Porta

That stack trace is from Meta-Inf’s Email This Issue (JETI) app, and the error means JETI couldn’t resolve any recipients from what you configured, so it aborted the send.

A Labels-type custom field doesn’t contain email addresses or users, so JETI’s recipient resolver finds nothing and throws NoRecipientsException. JETI expects recipients that resolve to valid emails (users, groups/roles, request participants, or a text field full of email addresses). If all candidates are filtered out by settings, you’ll also see “No recipients.

See the doc: https://docs.meta-inf.hu/email-this-issue/outgoing-emails/email-this-issue-for-jira-cloud-workflow-post-function

The best resolution is to replace your Labels CF with a Multi-User Picker (e.g., “Post-Action Recipients”) and point your JETI post-function at that field.

[Christos Markoulatos]

Hi @Jonathan Porta 

If you’re using Email This Issue (JETI), The NoRecipientsException means that the app couldn’t resolve any valid recipients. As far as I remember JETI only accepts email addresses or Jira users from supported field types, Text (with emails) or Multi-User Picker. A Labels field won’t work because its values aren’t resolvable to emails or users.

Either switch your custom field to one of the supported types or add an automation rule that copies label values into a Text field containing actual email addresses. Then configure that field under Advanced Email Configuration → Store non-Jira Recipients.

I believe this should work