What's the system impact on running a filter subscription across all users?

I've got a team requesting an email alert to be sent out to users when an issue due date is approaching. In order to ensure I capture whichever user may be attached to that ticket, I'd have to run a filter on project and due date, including assignee = currentUser() and attach the resulting subscription to the jira-users group. Is there an associated system load with running this search along all users?

2 answers

I would always reduce the number of issues to a minimum that are returned by any filter being used for subscriptions. For example using the condition of resolution is EMPTY to remove any issues that are already completed. 

I have 450 users on my instance and several similar subsriptions and there is no trouble. But I set it on different time (differs for 15 min) in order not to create long letter chain.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,305 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot