How to associate the issue type schema with my project. I don’t see the options that are written abo

[Tetiana Tuzova]

I created a project in Jira. I created additional issue types and sub-task types, and added them all to the issue type scheme. The instructions say that I need to link the scheme to the project, but I cannot select the project. How can I do this? I can't figure it out.

When I try to create a sub-task 'Testing' under a Task, I can't do it. The 'Testing' sub-task type doesn't appear.

[Trudy Claspill]

Hello @Tetiana Tuzova 

Welcome to the Atlassian community.

What type of project are you using?

• Go to the View All Projects page under the Projects menu. Find your project in the list. What does it say in the Type column.

If it says "Team-managed...", those projects don't use Schemes. Schemes are used for configurations that can be shared between multiple projects. Team Managed project customizations and configurations are project specific.

If you are working with a Team Managed project, follow the guidance here to add issue types:

https://support.atlassian.com/jira-software-cloud/docs/set-up-issue-types-in-team-managed-projects/

[Tetiana Tuzova]

     Hello @Trudy Claspill 

Thank you so much for the suggestion.

Yes, you are right, my project has type - Software development, team-managed. I understand that I cannot create my own sub-tasks right now. Could you please clarify the difference between the types team-managed and company-managed? How can I switch to company-managed progect?

[Trudy Claspill]

Hello @Tetiana Tuzova 

The big difference between Team Managed projects and Company Managed projects is that Team Managed projects enable the Project Administrator to customize the project with custom fields, custom workflow, custom issue types, and custom project roles. For Company Managed projects those customizations are managed by Jira Product Administrators. Because of these differences not all functionality that is available in one type of project is also available in the other type of project. For example there are limitations on how the Workflows can be customized in TM projects. There are documents that talk about differences between the project types.

https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/

It is not possible to switch a project from Team Managed to Company Managed. If you want a project of the other type, a new project of that type needs to be created. It is possible to move issues from the original project to the new project, but there is a risk of data loss. The process should be tested with a few test issues before it is used to move production issues in bulk. You can find more information on the risks here:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/