HOW CAN I GET A SINGLE TASK LİST FOR EACH ASSIGNEE?

Question

Hi  there i am using Jira 9.4.

Using Automation tool i created a global rule with a jql:

project in (P703116, P659289, P659290, P640041) AND statusCategory not in (Done) AND reporter not in (projettt_user) AND type = "Toplantı Aksiyonu" AND "Beklenen Hedef Bitiş Tarihi" <= 1w ORDER BY cf[15600] ASC, cf[14702] ASC

With this jql ai send and aouto-mail notifications for each task to assignees.

I am trying to figure out how can i send a single 1 notification for each assignee's all tasks.

Is there anyone who achieved this?

Trudy P Claspill · Answer

I am not aware of a plugin for Jira Data Center that does that, but you should search for yourself at https://marketplace.atlassian.com

ahmet can_h9zph4 · Answer

create a separate Lookup Issues action for each expected Assignee value

10x for reply. I am a Project Man. there are many stakeholders so the solution is not efficient 4 me.

I was using Raley add-on before but it needs Cloud license.

Is there any other Add-On that will work me?

Trudy P Claspill · Answer

Hello @ahmet can

I did not see your update. Notifications from the community were broken for a short period of time.

With a Schedule trigger when you include a JQL in the trigger then the remaining steps in the rule will be executed for each issue found by that JQL. That is why you are getting an email for each issue.

My first thought was to suggest that you remove the JQL from the trigger and use a Lookup Issues action to look up the issue list instead. You could then send one email for the list, formatting the content of the email to list each item returned by Lookup Issues. You can see an example of that in the documentation under the Lookup Issues action heading.

https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html

However, that does not give you a list per Assignee.

In Cloud there is a concept called Advanced Branching that would allow you to create a branch based on the distinct values in the Assignee field in the Lookup Issues results. That feature doesn't appear to be available with Automation for Jira Server/Data Center.

Without that you would need to create a separate Lookup Issues action for each expected Assignee value, including criteria in the JQL to select issues based on the Assignee. Then follow each Lookup Issues action with a Send Email action to send that list to the Assignee.