distinct.emailAddress not working

[Nils Herhaus]

Hey together, 

I followed this guide exactly

Link: Automation to send email only once per assignee  

However, I just sends multiple Emails to the same assignee everytime the rule gets executed.

Did someone experienced the same problem here and can provide some help?

Best regards

Nils 

[Nils Herhaus · Accepted solution]

Hi @Bill Sheboy , I attached the images of my rule workflow. It's not exactly the same, but it should work nevertheless. 

Problem: I still receive several Emails for each ticket.

Thanks in advance!

Best regards

Nils

[Bill Sheboy · Accepted solution]

Hi @Nils Herhaus -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

The likely cause of this symptom is you have added JQL to the Scheduled trigger, and so the rule is iterating over those issues also.

Please check that, and if the trigger has JQL, remove it and re-test.

Kind regards,
Bill

[Bill Sheboy]

Hi, Nils!

Please try to stick to one thread when posting; that will help others looking at this question in the future know if there are multiple solution approaches.  Thanks!

As I suspected, your scheduled trigger contains JQL, and it should not.  The rule is processing for each issue found by the trigger.

Here is the change you need:

• trigger: scheduled, and remove the JQL
• action: add another lookup issues action, using the JQL which was in the trigger
• branch: change the branch source smart value to {{lookupIssues.assignee.distinct}}
  • ...everything else is the same.

Please note, this is also what the how-to article shows.

[Nils Herhaus]

Hi it worked, thank you very much!

[John Funk]

Can you post your final rule for future users?

[Nils Herhaus]

Hi @John Funk here the final result. I hope this helps:

Its acutally exactly like here:
Link: Automation to send email only once per assignee  

[Idiyana]

will this work if i change the asignee with a multi user picker custom field?

[Bill Sheboy]

Hi @Idiyana 

You cannot change the built-in Assignee field to a multiple-select user field.

If instead you are asking if a multiple-select user field can be used instead of the assignee, the answer is likely "yes, depending upon your rule structure and actions needed".

And as this is an older thread, I recommend creating a new question and perhaps adding a link to this one.  That will ensure the maximum number of people see your new question to offer suggestions.

Kind regards,
Bill