Created 21 years ago. Unassigned and the last update was 8 years ago. This represents Atlassian more than anything. 

Addin my Vote - We need to create a Project for each new Client. I should not need to give my Project Managers Admin rights to the entire system, to do this basic task.

Hi, in case you are up for a third party solution that's hosted by Atlassian.

Project Templates for Jira offers an intuitive way to design custom project templates and allow non-admins to create Jira projects based on them.

• Customize the templates configuration to meet your unique requirements

• Give non-admins template specific project creation power 

• Customize the UX & information displayed to non-admins 

• Clone and predefine project versions, components, project role actors and issues including their hierarchy.

• Avoid the technical debt of unnecessary created Jira schemes/configurations

The app is built on Forge with no data egress, no sensible information stored and completely hosted in Atlassian's cloud infrastructure. 
Please let our support know if you have any questions.

@Derek Fields, I need these people to create projects which is why I'm complaining about it on this Jira Cloud issue thread about granular permissions to create projects. We usually have ten to fifteen new jobs a month and the Jira projects associated with them are created by their project manager or controls engineer. Right now that means every PM and controls engineer has to be a Jira administrator. My company is unable and unwilling to create a central Jira authority, right now it's just me trying to convince people to stop using post-it notes and I'm too busy to go around creating everyone's project for them.

@Roberto Ialino, archiving projects is a feature of Jira Cloud Premium which is double the cost of Standard. Using permissions to hide old projects works, but only for people that aren't Administrators, but right now everyone that cares is an administrator, so we can't actually hide these things.

Hi @Derek Fileds for instances with 2k users you need a certain number of administrators since UNFORTUNATELLY the admin permission are not granular enough.
On large organization you cannot apply adminin permission for create new project (for example) because the same permission enable the user management. This have completely no sense expecially now that there is an increase of security requirements.
Atlassian NEED TO DO SOMETHING since this administration model does not work at all.

@IBrown_BluePrint - if you create a permission schema ad hoc that restrict to only some people the visibility (only admins for example), you can archive projects.
About the cost you are mentioning is not clear to me at all.

Best regards

@IBrown_BluePrint - Do you really need 20 Jira administrators? In my experience, even the largest organizations can usually get by with 2-3 Jira administrators. When I see that number of admins, it makes me wonder whether there are too many cooks in the kitchen. It makes me shudder to think that they are "un-savvy enough to ..." Why would you give people who don't know what they are doing Jira admin permission?

I talked my manufacturing company to move to Jira from literal post-it notes and it's junk like this that is getting me tons of pushback. I now have 20 Jira administrators, most of which are un-savvy enough to delete the entire site if they got lost enough, just so they can create projects.

The real kick in the pants is we've already got multiple pages of projects in less than a year and we'd have to literally pay double the price to unlock the ability to archive them. Can't hide them with restrictive permissions either because everyone has to be a damn admin to create new projects!

Sad!

This isn't going to get implemented in any of our lifetimes. :')

High priority for 6 years.

These kinds of "issues" that stay without an update for years despite increasing number of support requests makes me want to migrate away to a solution like ClickUp.