Can't associate issue type schemes with various projects

[Adam Bunn]

Hi,

We've recently begun using Jira software cloud as a team of knowledge base content creators in our business. I'm the manager of the team and will be looking at usage reports for my team. 

However, I'm experiencing some issues with the issue type schemes. My understanding here is that setting up a scheme should allow me to define the issue types available across all projects we set up. However, there doesn't seem to be an option to select a scheme when setting up a project. 

I'm currently in a situation where each of my team's projects has it's own issue types set up to be the same, but obviously from a system pov, they're all unique. So when it comes to reporting on volumes of 'x' issue type, I have multiples with the same name and have to collate. 

In the settings menus, I can create issue types and schemes in addition to the default but on the 'associate' screen, I can only see 1 project which is a company-managed kanban, the rest of my team's projects (team-managed) don't appear. Does this mean I can't achieve this uniformity across my team?

[Nic Brough -Adaptavist-]

To answer the implied question:

"My understanding here is that setting up a scheme should allow me to define the issue types available across all projects we set up."

That is only true for company-managed projects.  Team-managed projects have their own way of doing issue types and they're set up on a project by project basis.

[Fabio Racobaldo _Herzum_]

Hi @Adam Bunn ,

welcome to the Atlassian community!

You can create projects with shared configuration. This is something available just for company-manged project (it should be your case).

During project creation wizard, when you add project name and key, you need to select "Share settings with an existing project" and select original project setup that you want to use for this new project.

Hope this helps,

Fabio