Executing a scheduled, global automation on behalf of every single user

[Leonard Winck]

Hey there, we're looking forward to write an automation which will send a mail to every employee every week, containing a list with their tickets which aren't finished yet.

We'd rather not use the subscription filter, since it's not as versatile, the user can unsubscribe and it's harder to edit the templates.

For one user this works great using a scheduled automation (with bulk processing to not create a flood of mails for every single issue) and then filtering for "statusCategory != Done". Then, the automation is set to send a mail to the assignee.

This was the most logical system we could come up with, however (obviously) it leads to problems - the mail is containing EVERY open ticket and is being sent with identical content to all assignees.

So my question is: How do we execute an automation on behalf of every single assigne in a group? This way, the automation could just be set to filter for "currentUser()" and, since it's being executed on behalf of everyone themselves, it'll only contain their content and'll only be sent to them specifically.

It'd be kinda complicated to write a  new automation for every single user.

[Artem_Danylkov_SaaSJet_]

Hello Leonard,

We understand your problem so we would like to offer you a great solution. It’s Boomerang: Reminders for Jira Issues, this addon help you to remind teams or users about important issues in Jira Cloud.

You can use our plugin to create periodic reminders for repeating activities: ones, daily, weekly or monthly, or set automatic reminders on comments to issues and at the same time

as notifications on email.

Best regards

Artem

[Jack Brickey]

What about a solution that simply directs the user to a dashboard or filter? Sort of a reminder email that says “hey check your open issues”. You could use automation to send an email weekly to all users and include a link to the dashboard or filter. The dashboard or filter would use currentuser ().

[Leonard Winck]

Unfortunatly, that doesn't seem to be a valid option. The list has to be sent in the mail, like it is using the subscription option. That was the main requirement.

[Jack Brickey]

have you tried simply using currentuser() in the filter w/ subscription?

project = abc and assignee = currentuser() and statuscategory != done

according to this article for cloud I find the following:

Be aware that the emailed filter results will be specific to each recipient. For example, if the filter uses the currentUser() function, the search results will be evaluated with the recipient as the current user. This doesn't apply to distribution lists (group email aliases).

[Leonard Winck]

I have tried that, however, it'll then only work for me, since I'm the Actor.