Avoid Issue Security Scheme changes

[Arianna Fabbri]

Hi,

we need to setup a reserved project so we need to associate to it an issue security scheme that has not to be changed from anyone except for specific users.

Have you any suggestion regarding this topic?

We would like to avoid that users with JIRA Administration Global Permission can change the security scheme of this specific project, or any other way to avoid that these user can change visibility settings.

Thank you in advance

Regards

Arianna Fabbri

[Nic Brough [Adaptavist]]

There's no way to stop the administrators changing things, as that is their job.

Essentially, you have to trust someone to look after your system, and that's what your admins do.  You should have a small team of people that you trust running JIRA.  (And enable the admin logging so you have some trace of what they've been up to)

[Arianna Fabbri]

Hi Nic, thank you for your quick answer. So, if I enable admin logging (from where?) I'll be able to see if someone will change the security scheme? Thank you Arianna

[Nic Brough [Adaptavist]]

I'm really bad at memorising the admin menus in different JIRA versions. I think it's Admin -> System -> Audit log, but if not, then it's definitely called "Audit" something, so a search in the admin section will definitely find it. It logs a *lot* of admin actions - you'll usually see patterns like "lots of user changes" if you rely heavily on groups, and batches of "project scheme changes" when an admin creates a new project. But a search for "scheme" or "security" should narrow it down lots.

[Arianna Fabbri]

I've checked and unfortunately it logs only events like: "Issue security scheme added to project" "Issue security scheme removed from project" Nothing about changes of a security scheme.

[Nic Brough [Adaptavist]]

Bother, I thought it was trapping scheme edits too (not the users/groups, but the "add new level" and "change rules for level" type stuff) Sorry.