nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

Darryl Lee

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

giphy

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

Danno

OK, I just don't get it. I'm trying to do this very thing without having to parse assignees. It's a simple Lookup search and send email using the exact text of @Darryl Lee example and my email comes back blank. I've been able to send emails before w/o any issues but now it doesn't work. This is the second automation this week I've had trouble with.

Jira automation fail.png

Jira automation fail blank email.png

All comments

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.

unknown

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

Darryl Lee

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

giphy

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 :^)

Benajmin Kun

@vdhanorkar @Bill Sheboy @Darryl Lee @[deleted]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

Danno

Jira automation fail.png

Jira automation fail blank email.png

Bill Sheboy

Hi @Danno

If you run your JQL manually, does it have any results:

worklogAuthor = currentUser() AND worklogDate >= startOfWeek() ORDER BY updatedDate DESC

And, who is the rule "actor"? If it is the default of "Automation for Jira" it will likely not find any issues. If it is "user who triggered the event" it may find them.

You could instead change the JQL to used the {{initiator.accountId}} when checking the worklogAuthor, and leave the rule actor unchanged.

Kind regards,
Bill

Danno

@Bill Sheboy that is the weird thing about this. The Lookup Issues action does find the correct number of issues (5). I validated it in the automation setup. My original intent was to get the number of issues a user logged time in for a given period, in this case, startOf Week(). I didn't include the rest of my automation yet because I broke it earlier when I started to set it up to email the user. When it came back with the blank email I figured I needed to back up and get that working so I moved it to the position it's in currently. As you can see it still isn't working.

I've included the rest of the automation and the audit log here to verify the original lookup worked.

Jira automation fail blank email auditlog.png

Jira automation fail blank email lookup filter results.png

Bill Sheboy

Please note in the audit log that the Lookup Issues returned no issues. That is likely because the rule actor is the default of "Automation for Jira", and that is then used as the currentUser() in the JQL.

Please try changing your Lookup Issues JQL to this and run the rule again:

worklogAuthor = {{initiator.accountId}} AND worklogDate >= startOfWeek() ORDER BY updatedDate DESC