Why does selecting a Jira notification scheme requires global admin rights?

From the documentation I have learned that selecting a notification scheme for a project requires global admin rights. I do not see the reason why this should be possible for the project administrator. If the Jira administrator has defined a set of notification schemes it should be problem if the project administrator chooses the apropriate scheme for his project.

Does someone kno the rational behind this, or this there even a way to change this behaviour?


1 answer

1 accepted

Accepted Answer
1 vote

Because it's possible to select notification schemes that are inappropriate. Some sites I've been to, it would work fine. At most, it's not - most project admins quite happily select schemes that they simply don't understand, and end up spamming all sorts of people (It's not just notification schemes, most schemes are too intricate to be trusted to project owners to select the right one, but notification schemes are definitely the ones that cause the most complaints from the users because of the spam an incorrect one can generate).

There's no way to change it without editing the code for project administration.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

24,725 views 2 7
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