Is there a way to send one email to one assignee with email body containing only assignee's issue

[vdhanorkar]

I have created one automation rule and I am trying to send a list of issues to the individual assignee through a single email but could not do that. Users are receiving multiple emails also they are receiving other's tasks details in the email body(See the second screenshot).

Is there a way where I can send a list of issues to each individual through a single email?

[Darryl Lee · Accepted solution]

After proudly showing my solution to a colleague he commented: I was just using filters + subscriptions. To which I replied...

He's exactly right. That's way easier. And the emails look much nicer.

Your filter would be something like:

assignee = currentuser() and resolution is EMPTY

https://support.atlassian.com/jira-work-management/docs/work-with-search-results/#Workingwithsearchresults-subscribeSubscribetosearchresults

[Bill Sheboy]

Yes, and...after you get the people to subscribe to the filter  :^)

[Darryl Lee]

It would help if you can screenshot your entire rule.

If you are using a JQL condition then you need to take the email action *outside* of that condition because it's executing for *every* issue it finds.

Not sure why it's showing other assignee's issue unless there's a problem with your JQL.

So yeah, seeing the whole rule would let us better help you.

[Darryl Lee]

Sorry, I hadn't had enough coffee this morning. :-}

Upon re-reading your question, I'm guessing that you are doing a lookup of issues where Due Date IS EMPTY. 

So yeah, I think the problem is that unless you constrain the query to a single assignee (and then you'd have to create rules for every assignee), then it's going to (apparently) mail every assignee the list of everyone's issues.

[vdhanorkar]

@Darryl Lee Thanks for looking into this, here is the screenshot as you requested.

[vdhanorkar]

@Darryl Lee I found a similar ticket https://codebarrel.atlassian.net/browse/AUT-1975,

but I am confused about whether this problem got solved or still exists, as per the task description it is not possible to send an email to one assignee with an email body containing only the assignee's issue. 

Could you please confirm? If it is got resolved then please tell me the solution.

[Darryl Lee]

Yeah, I don't think they should've closed AUT-1975 as a duplicate because while AUT-684, AUT-285, and AUT-105 are related they are not the same.

So yes, as I suspected, your query will always return a list with multiple assignees, and so there's no mechanism to iterate through each assignee and send a list with only their issues.

Hum, if you could iterate through the list of assignees, you could probably use filters to do something like:

{{#allassignees}}
  {{#lookupissues}}
     {{#if(assignee.accountId == allassignees.this.accountId)}}
        * {{key}} | {{summary}} | {{assignee.displayName}} | {{url}}
     {{/}}
  {{/}}
{{/}}

But the problem is 1) I don't know how to get that list of assignees out of Jira, 2) I don't think you can have nested lists in Automation. :-/

[Darryl Lee]

Oh man! I'm getting close! Got the list of assignees and can iterate through it with Advanced branching, accessing {{lookupIssues.assignee.distinct}} like so (this is the "For each" section that shows up in the full rule at the bottom:

But the problem then is my "filter" can't access the thisassignee variable within {{#lookupissues}} for the email body. I unsuccessfully tried:

{{#lookupIssues}}
{{#if(assignee.accountId == thisassignee.accountId)}}* {{key}} | {{summary}} | {{assignee.displayName}} | {{url}}{{/}}
{{/}}

(which gave each assignee a blank email)

and

{{#lookupIssues}}
{{#if(assignee.accountId == {{thisassignee.accountId}})}}* {{key}} | {{summary}} | {{assignee.displayName}} | {{url}}{{/}}
{{/}}

which failed with: 

Error rendering smart-values when executing this rule:

Here's what I'm working with. Any thoughts, @Bill Sheboy?

[Darryl Lee]

Ah, think you solved this previously, @Bill Sheboy by adding another JQL query for each assignee. Clever. https://community.atlassian.com/t5/Jira-questions/Smart-Value-Filtering-Comparing-Two-Lists/qaq-p/1959275

For option #3, you could use lookup issues and advanced branching to then notify the people...or send yourself n-emails (one for each person).  Here is an example rule to do this:

Let me give that a hack.

[Bill Sheboy]

Yes, and...

I believe the requestor asked the same question in this other thread, where I also answered: https://community.atlassian.com/t5/Automation-questions/Re-Re-1-Notification-per-assignee-via-Automation-on-Jira/qaq-p/2092384/comment-id/4502#M4502

[Darryl Lee]

Success!

Full rule: 

And details on the new second Lookup:

So there you have it. BTW, I corrected your original mail body @vdhanorkar because you had {{issue.summary}} when you just need {{summary}}.

[vdhanorkar]

Thanks @Darryl Lee , it works to me, thanks for looking in to it.

[Paul Stahlke]

@Darryl Lee I tried to implement this using your latest screenshots. While the email itself looks perfect and does to the correct assignee, it sends it as many times as there are issues for the assignee. It's as though it's iterating through all the assignees in the first lookup rather than just the "distinct" assignees. I am running in Jira Cloud. Any ideas?

[Paul Stahlke]

Disregard! I was using the Schedule trigger and have the habit of applying a JQL search there as well, so it was iterating through that. Removed it, and it works beautifully!

[Dan Tombs]

Hi @vdhanorkar

I think the alternative would still lead to running a multiple send email and lookup action etc. But branching out and specifying individual users could also work

[Benajmin Kun]

@vdhanorkar @Bill Sheboy @Darryl Lee @Dan Tombs Hi guys need your help, I tried to build this automation but I get an empty assignee.displayName 

[Bill Sheboy]

Hi @Benajmin Kun 

Please check your smart values in send email, as you have a typo in {{assignee.displayName}}

And...you seem to reference an issue's fields outside of the Lookup Issues iterator; before it specifically.  Try using {{thisassignee.displayName}} or {{lookupIssues.first.assignee.displayName}} for that one.

Kind regards,
Bill