Why can't my team create company managed projects unless they are site admins?

Question

i don't understand the permissions. unless they are site admins, users cannot 1) invite their team to jira to collaborate 2) create company managed projects. How can i make sure everyone gets access in the organisation but without giving everyone advanced admin rights?

Jason Forester · Answer

I guess I get what you're saying, but if we want a templated system that keeps users from setting up any sort of a mess, the only way is by using company managed and copy settings from previous project. The fact that users (say PMs with the right privileges) can't do this is still crazy to me, and fundamentally makes Jira a not-necessarily-for-us product.

Nic Brough -Adaptavist- · Answer

Welcome to the Atlassian Community!

It's because project creation is more complex than just "choose a scheme" - some workflows won't work with certain field setups, security, permissions, notifications and and and, and you need an admin to understand.

I agree that it would be nice to have a simple "please create a project for me, using the template X", but Atlassian have never implemented a templating system.  The closest they've got is the "create CMP and use the settings from project Y"

Jason Forester · Answer

I know this is months old, but Google found it for me...

You wrote "Company-managed project configuration is limited to Jira admins."

I agree 100% that the configuration needs to be controlled. But once that config is done, why can we not let others create projects based on that configuration. I can't understand the logic in needing to ask an admin to create a new project every time, once the entire config has been created and locked down.