8288d767919c you can disable it by global permissions and leave it only for admins, but even admins can make mistakes, this is my particular problem. We create a lot of TEAM managed projects accidentally and dont want them at all.

The admins, to my knowlegde, cannot be taken away the permission. If you still do it (jira-administrators group can be removed), I still have the default option set to TEAM-managed. This is really annoying.

• The default should be the restricted
  OR
• The last choice shall be remembered
  OR
• The option should take TEAM out when the permission was removed (my comment above)

It is a problem that users can create these projects, you need to remove the cloud function

Rather than preventing admins, make life for admins easier by following what was questioned before

• So as Org Admin, why is it defaulting to "Team Managed" projects before "Company Managed"?

I create projects all the time and are bothered, that I need to switch the type to COMPANY every time. Fix this

Please remove this.  As a org, we agreed to never use team-managed projects, but every once and a while an admin forgets (or is new and didn't know the policy) and creates them.

Team-managed project should not be created if the Global permissions is set to not allow anyone to create them. Ideally, the option to create Team-managed projects should disappear if the Global permission is set to not allow anyone to create them. This is a bug! Please fix ASAP!

So as Org Admin, why is it defaulting to "Team Managed" projects before "Company Managed"?

In the past month, there have been dozens of Team Managed projects created by accident due to this. Yes, we can learn to resolve this via process, but why should we have to? Why why WHY would you default Team Managed first? That has to be one of the classically worst decisions in a history of bad decisions. If you are going to continue to make Team Managed be a thing then you need to come up with a better conversion path and/or a way to set the Default Project to Create to Company. Because the current setup is costing us time and money. And frankly it is bad design, bad planning, and really really really frustrating. I've been using Jira for over 20 years just fine without Team Managed. All you are doing is creating feature bloat for a feature that no one wants and no one asked for. Please find a better solution and stop creating more work for us. Why do you keep hamstringing the partners that are trying to help you be a viable product! It is getting harder to justify the cost of Cloud to clients when you keep adding to the maintenance and overhead from the get go.

Please kill the team projects. They are horrific. The amount of extra that is has caused to fix this issue is crazy. 

The issues these projects have on our backend is horrible, which was why I did not, and do not, allow the use of Team Managed or Next Gen projects at our company.  However, Product Discovery is another nightmare that causes all the same issues.  I am pushing for our company to eliminate the use of it.  I have already restricted our use that product, to 1 single project, for all three of our affilates.  Not a popular decision, but reduces the impacts.  On another note, the teams are starting to find that Jira itself might actually be of better use then JPD anyway, so fingers crossed, they elect on their own to walk away from that app altogether.

Unfortunately, this will still not cover the situation of the new Jira Product Discovery projects which are just team-managed projects or using the same mechanics/structure underneath.
This will mean Atlassian can not disable this type probably, unless JPD project use a different 'type'.
:thinking:

Agreed. It's only our admins who are creating projects anyway so the current limitation does nothing.