Admins can now configure issue security levels they don't belong to

[#1]

We’re giving admins more control and teams more confidence when it comes to issue security

Jira Admins no longer need to add themselves to every security level in order to configure issue security.

It’s crucial for many teams working in service projects to have confidence that any sensitive information collected from requests can only be seen by specific people - and with issue security that’s more than possible.

Issue security allows you to manage who can view certain issues, giving you the ability to lock down issues to certain users, groups, roles, organization and more.

We announced a bunch of exciting improvements to make it easier to manage these security levels when configuring your request types to give you more control and confidence.

One of these big improvements was giving admins the ability to view all security levels available in their project during configuration, with levels broken into Member and Not a member. Previously admins didn’t have this ability; needing to add themselves to all security levels to be able to set them.

With this small but mighty improvement, teams can have even more confidence that issues are locked down to the right people with even admins not having access to confidential information contained to sensitive issues.

[__ Jimi Wikman]

An interesting change, but considering you have to test the configurations and that as an admin you can add yourself to any configuration anyway, this does not really provide a very hard layer of protection.

It is a good step, don't get me wrong, but just like groups are black holes, no one would actually know if someone with admin powers would assign themselves access unless they read the logs.

If this is extended into Guard for example where there can be a notification for protected security schemas for example, then this would be good. If it is also added to protected projects somehow, then that would be even better.

Good first step, but can be improved :)