User can still trash company-managed projects after I removed him from site-admin group

[Laurien Scoville]

I'm new to admining a very messy instance of Jira, and we had too many site admins. I've removed most of them from the site-admin group and all other admin groups, but it seems like one, perhaps more, can still delete/trash company-managed projects. Is there something I'm missing or is this a bug I need to escalate to Atlassian? This is a big problem where integrations are concerned.

[Peter DeWitt]

@Laurien Scoville The user may still have access through the project level permissions. 

1. Open the project of concern
2. Open Settings (Gear, bottom left-hand corner)
3. Select Permissions (may need to scroll down)
4. Check the Project Administrator Permissions

[Laurien Scoville]

Is there no way to remove the ability to delete the project from a Project Administrator, then? This person needs to remain the Project Administrator.

[Peter DeWitt]

@Laurien Scoville , Unfortunately no. my assumption is that this person is a release manager (or fills that role) and needs to be able to update components & versions. Unfortunately, in cloud, the Administer Projects permission allows a user to do the following:

They can: 

• move projects to trash,

• edit project role membership 

• edit project components, 

• edit project versions,

• edit some project details – project name, URL, project lead, and project description.

for reference: 

https://confluence.atlassian.com/adminjiracloud/permissions-for-company-managed-projects-1001823931.html

There is an open suggestion to allow these to be configured separately:

https://jira.atlassian.com/browse/JRACLOUD-34015

I would vote & watch this request.

-pjd

[Laurien Scoville]

Thank you so much for your thorough responses, they have been very helpful!