You can make it such that nobody, except those with the Administer Jira permission, can create new team-managed projects.
Removing this permission does not delete existing team-managed projects. Users with the Administer Jira permission can always create team-managed projects, even if that group is removed from this permission. (If you'd like to prevent even admins themselves from creating new team-managed projects, please vote for https://jira.atlassian.com/browse/JSWCLOUD-21477 as suggested by @Vero Rivas
You can remove this permissions via the Global Permissions settings in the System settings (you will need to be a site admin or a Jira admin to do this). Here's some screenshots to guide you :)
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! Super helpful!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Emily for this ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, just what I needed to stop some of the annoyance with users creating Team managed project and then realising the limitations after. Then requesting a new company managed, leaving the team managed and then I can find and clean up or start all the migration work. Waste of time this functionality.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I still have one remark that needs to be given importance here.
I just wanted to give the site-admins the right to create team-managed projects. However, jira-administrators could still create these projects. After reading several times, I came across the following section:
Users with the Administer Jira permission can always create team-managed projects, even if that group is removed from this permission.
With this, it's either all or nothing. So if you are an admin you will always bes able to create team-managed projects. no matter what the global permissions say
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Found out that too. I would really love the ability as site/org admin to totally remove the Team Managed project, can't see the purpose, it impose silo work. Just my opinion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Team Managed Projects have been a huge frustration for me as an Admin. Users being allowed to create them, and then "hide" them from Admins if they are not added as a Users on the project (we have 3 legacy Team Projects in use our and our Team Projects cannot be "public" due to and the fact that we have external Users with specific permissions to allocated Projects ) is very counter productive. I have taken away all permissions, but Users can STILL create Team Managed Projects! Does anyone else have this trouble? I may need to start a new ticket :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Me and you both... God I hate administering this platform.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've got the same problem....... @Christina Payne or @Joshua Cedeno have you found a solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The only failsafe I have found that works was creating a web hook that sends me a direct message to my Teams messenger, letting me know someone created a new project. Just more babysitting that isn't necessary, IF Atlassian can just allow Admins to disable the team managed project option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply. I will think about a similar workaround, somehow we have to manage it :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.