Hi Everyone,

I know you all prefer to have this feature built in from Jira.
But as we all know that can take years!

We created a (paid) plugin Delegated Administration for Jira (support DC from Jira 9.xx)
This plugin let you delegate the "create project" permission and some other admin permissions if you want.

This plugin is all about delegating administration permissions, so if there is something you wish you could delegate and not exist in the plugin, please open us a ticket request and we will add it.

We are giving 20% discount till end of 2023, just contact us via ticket and we will give it to you.

Hope you will find it useful

Thanks,
Pitronote Team

This would be a useful feature for our company.

I tought that the vote function was there to indicate my interest in a feature request...

But just to make sure that Atlassian does understand that I'm still interested in that feature.  I will not repeat all the reasons why I'm still interested, it's been all clearly documented in the other comments.

Here it is written clearly:  I am still interested in that feature!

Thank you

Still a highly needed item. I'm honestly shocked this is still something you're again only "Gathering Interest" in... why Atlassian does not have this on the roadmap yet is unbelievable. This is a SECURITY ISSUE!! In this age where we are constantly evaluated for INTERNAL bad actors... how are you, in good conscience, letting this stand? You are giving large organizations zero choice in how to handle securing the Jira environment. There is literally no reason for someone to have ADMIN privileges for something as simple as project creation. Over half of the items in your roadmap list are far less consequential to organizations than this continued oversight. So, to be clear, YES - I am still interested.

I am glad I am not alone with this..  It finally hit me when I am slowly wandering back into Jira Administration.. this would be very handy to have  all the above comments reflect the same concerns with having this permission without having to assign the user as an Administrator.  It would be nice to have, so if my comment upticks it, great!!

So....  just hit this issue for the first time and browsing google to see if anyone else felt this was a huge missing item from Jira permissions.  Reading this is a bit disturbing, as an organisation that is currently considering a big increase in Jira usage.

It's nice to be in a crowd of  1200 (socially distanced) upvoters, but it does make me wonder how many votes are required before Atlassian will fix a defect - because this is a functional defect.

For those who find it useful.

We created a plugin that gives this feature (among other things).

Delegated Administration for Jira

Here is also a 50% off coupon: https://promo.atlassian.com/JMCLDP

Best Regards,
Pitronote Team

2185e9be7a59 thing is that Atlassian (company) just don't care about us (you, me and rest of their customers).

Allow me to present you these proofs for my claim:

1. (shameless plug: this is my comment ): https://jira.atlassian.com/browse/JSWSERVER-9167?focusedCommentId=1611502&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1611502
2. my favorite comment (made by john31) that pretty much sums up how Atlassian (company) treats all of us: https://jira.atlassian.com/browse/JRASERVER-1431?focusedCommentId=1622073&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1622073

Note to Atalassian (engineers) staff that actually does all the work (people in development, QA, infrastructure, support, etc): I actually appreciate your hard work and I do understand that your matrix (operating systems/databases/legacy software code) is far from easy to deal with. Every piece of software has some bad parts (it is what is it). I assume that even people inside Atlassian have mixed feelings about their own product(s) (something similar to this guy: https://www.youtube.com/watch?v=uxC1fPE1QEE )

My critique goes to upper management only, i.e. to Atlassian (company).
Shame on you Atlassian (company)

How is it that a ticket regarding a very basic but important security feature that has been opened 17 years ago  and has gathered over 1000 votes (4th most-voted open issue) still hasn't managed to get on your todo list?

Please mkowalska or  anyone else from Atlassian give us a feasable explanation of why you are ignoring a clear customer desire for this feature and don't fend us off with that generic workflow for feature suggestion. I'm sure that issues like JRASERVER-70821 (basic auth behind a reverse proxy using the Jira app, 1 votes but in progress) or JRASERVER-65812 about adding some debug logging for edge-case situations (0 votes but in progress) are also imporatant, but I'm probably not bright enough to comprehend why these are deemed more important than this feature that should have been implemented in Jira 0.0.1.

IMHO there is only one correct action to take here, and that is to get this issue in progress.

This has been here quite awhile.   Please look for a solution to this. Thank you.