Delete Project permissions

[Casey-Lea Olson]

I have recently have someone delete a project, which deleted all the time off the project since November, this has of course cost a lot of extra time relogging etc. 

I cannot find where I can revoke ability to delete projects, this should only be allowed to be done by Jira Admininstrators - please help

[Niranjan]

Using script runner script fragments, you can hide "Delete Project" permissions for all. You can modify the script fragments when you perform a project deletion. This can prevent unintentional deletion of projects. Works with server script runner.

[Casey-Lea Olson]

Thank you for the suggestion, I noticed today that Jira has actually added functionality that you do not delete the project outright anymore, it is moved to 'trash' which the admin can restore from - it stays there for 60 days 

Nice one Atlassian :)

[Joe Pitt]

This won't help your current problem, but may stop more issues.

Put JIRA under CR

 I STRONGLY suggest you treat JIRA like a production system, put it under change control (CR), and track all requests for any updates, especially new projects, new custom fields, changes in any of the schemes, etc. That way at least the reporter will know when the actions happen and you'll have a audit trail. I've worked many similar tools to JIRA and too many times no one knows anything about why they are configured why they are because there is no requirements or CR. Things are just done based on emails that have disappeared and hallway or lunch conversations.  

If you don't already have a separate change control tool create a JIRA project. I use a basic workflow with a few custom issue types:

Custom field: with a select list of create, update. The description would be to create a new field or modify a current select list, buttons, etc. of a current one

Create Project: I would have text fields for issue types, custom fields, select list/values, per issue types

New Issue Type: description would include all fields and workflow desired.

Workflow: Select list of Create, update, delete. Description of what needed.

Other: Select list of Notification Scheme, permission scheme, field configuration, other

This should get you started. If you aren't familiar with your CR process there should be a configuration management person to talk to.

The goal is to manage what you do and be able to track who asked for what. For instance, if someone wants a new custom field you want to check to see if there already is one you can use that they don't know about. JIRA will let you have multiple custom fields with the same name, which will just confuse you.

[Casey-Lea Olson]

Thank you for your response. So we do have limited admins who can change fields and workflows etc. 

The person who deleted the project is not a site administrator so I did not realise that just anybody can delete a project, I am trying to find a way to limit that so that only administrators can do it, that way there needs to be a 'formal request / change' as you mentioned above and not just have random users deleting a project on a whim. 

[elenushhh]

Hello @Casey-Lea Olson ,

You should verify on the users list, from Administration -> Users if the person who deleted the project has site admin permission. On project's permissions scheme you cannot give that permission, so I guess the only problem might be the role. 

[Casey-Lea Olson]

Thanks Elena, the person is not a site admin, and I cannot find that permission anywhere :( I will keep looking, and if I can't find it I will log a ticket with Atlassian :)

[Severin Prothmann]

Hi @Casey-Lea Olson 

The User Role "Trusted" is also able to delete projects.
Just had the same issue. After changing the Users role from "Trusted" to "Basic", the specified user could no longer delete a project.

Cheers,
Severin