Why can I still archive issues even after I removed all archive permissions from a project?

[Sarah Jordan]

I would like to entirely disable the ability to archive issues in my project.  In my permission scheme, the following permissions are currently blank (not granted to any users):

• Browse Project Archive
• Archive Issues
• Restore Issues

However, even after setting the permissions appropriately, I am still able to archive an issue by selecting More -> Archive from the menu.  Can someone please tell me how to completely disable archiving in my project?

[Jack Brickey]

That is interesting. So are you saying that someone that does not have the aforementioned permissions is able to archive issues in the project? Are these users admins?

[Sarah Jordan]

@Jack BrickeyI was able to investigate this issue further a little while ago.  I am a member of the jira-project-administrators group so I have permission to do lots of things (including archive issues).  I temporarily assigned one of my team members to the Administrators project role.  I then asked him to try to archive an issue.  He was unable to do so because the More menu did not contain an Archive option.

The moral of the story appears to be that the archive permissions in a permission scheme have no effect whatsoever on members of the jira-project-administrators group.   They can archive whatever they want.  I find this bothersome as I would like to disable archiving for everyone (including myself) until such time that we feel it is necessary to archive issues for clean up purposes.

[Jack Brickey]

that would be consistent with my expectations. 

[Sarah Jordan]

@Jack Brickey Just to be clear, you expect it to work the way it is currently working or you share my expectation that permissions should be explicitly granted to users / groups / project roles in order for the given action to be allowed?

[Jack Brickey]

i would i=expect it to work as it is. admins are special cases.

[Sarah Jordan]

@Jack Brickey I actually expected that explicit permissions would be used for everyone, including admins, rather than admins having "magic" permissions behind the scenes.  I mean, isn't the point of a permissions scheme to explicitly grant access to only those who should have it?