We recently had an issue, where the jira-users group has been made a member of the Users role in one of the projects, and having forgotten that, one of the administrators has changed the notification scheme of that project to send email to member of the Users role when a new issue is created.
This resulted in two emails being sent out to 8000+ users.
Is there a way to prevent this in the future? Since we have quite a few users, some of them are project administrators of their own projects.
Can we either prevent JIRA from sending out an excessive amount of email (let's say over 1000) triggered by one single event? Or can we prevent users from adding the jira-users group to any role in the projects? Or is there any other way we could prevent this?
Maybe write a a simple script that do DB select (select all "jira-users" from roles) and scedule it. Then configure that if there is a results it sends you email. Because I believe that, if you will send email to 1000 users instead of 8000 will still be unacceptable.
The problem is that we have thousands of developers working on a little south of 1000 projects. That's not something that can be managed centrally. This is why we assign project administrator permissions to certain people in every project, thus they are able to assign users or groups to roles within their own projects. Also, we only provide a number of notification schemes, from which they can select the scheme they would like to use with their projects.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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