How do you change project type at Site Level?

[Jeff Coleman]

Want to give the option of choosing a Team or Company managed project types for all the templates (Work Management>Design, etc).  As Org/Site Admin I do not see that option and cannot find information on how to do that.  Thanks.  JC

[Trudy Claspill]

To whom are you trying to grant those permissions?

Jira natively allows only Jira Administrators to create Company Managed projects. There is no option to make that available to non-admins. Jira does allow you to grant access to non-admins to create Team Managed projects, specifically, through the Global Permissions.

There was a third party app that I used with Jira Server that allowed us to setup up "templates" for Company Managed projects, let users make requests for new projects from among those templates, and allowed delegating the responsibility to non-admins for pushing the button to actually create those projects. The app is called Delegated Project Creator, and I see it has now become supported for Jira Cloud also.

https://marketplace.atlassian.com/apps/1211157/delegated-project-creator-for-jira?hosting=cloud&tab=overview

[Jeff Coleman]

Thank you for the info, Trudy!

My first question was about changing some of the templates from Company to Team managed and disovered some templates are Company managed only and cannot be changed to Team. I just had to understand  how to set up the right permission scheme for the Company-managed projects so that each Group/Team can only access the project they are assinged to.  It is not super intuitve, but these instrcutions helped. 

To have a group with access to only one project, you'll need to change the Permission Schemes associated with the projects in your Jira. To do that, you'll need to:

1. Create a group for your external users and grant Jira Access to this group, on Product Access
2. Add the users on the external user's group and remove these users from the jira-software-users group
3. Create a copy of a Permission Scheme, on the Permission Schemes page
4. Change the Permission Schemes associated with the projects you want to restrict. You have to remove the application access(any logged in users) and add the jira-software-group with Browse Project permission, so only your internal users will have access to these projects
5. For the Copy Permission Scheme, you can either user application access(any logged in users) or use the external user's group on Browse Project permission. You'll need to add the jira-software-group in order to grant access permission to your internal users
6. After that, you need to associate the Copy Permission Scheme to the project you want to be visible for your external users. To do that, you need to go to Project Settings > Permissions > Actions > Use a different scheme

[Heather Ronnebeck]

I would review this page for creating company-managed projects - https://support.atlassian.com/jira-cloud-administration/docs/create-and-edit-a-project/

and this page for team-managed projects - https://support.atlassian.com/jira-software-cloud/docs/create-edit-and-delete-team-managed-projects/

and if you're trying to migrate between either type this page - https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

A way you can restrict the types of projects being created is by limiting who has administration abilities in your instance and then setting a standard across your org to help your admins understand which projects can be created.