In system settings, why aren't all the default issues types listed?

[Melissa S]

When creating a new instance of Jira Software, before creating any projects, when viewing the System Administrator's 'Issue Type' page, only Epic is listed? 

[Nic Brough -Adaptavist- · Accepted solution]

Jira used to ship with a a set of standard issue types, and no different project templates - you had to a create a project, then create and give it a new issue type scheme when you needed a different set of issue types.

Atlassian added project templates a while ago, which allowed us to create projects pre-configureed with different default schemes (including different issue type schemes).  As they went further with these, they gradually removed all the default objects behind the schemes, so that they only got created when you created a project that needed them.

So, an "empty" jira now not only has no pre-defined schemes, it doesn't have any of the configuration objects for the schemes either.  It makes some sense - why have an issue type or custom field that none of your projects are using?

The default objects only get created when you first create a project that needs them now, and that includes the list of issue types!  Epic is an exception because Epic has a pile of unusual coding behind it and Jira Software needs it to be set up in a very specfic way to make it work properly.

[Ollie Guan]

Hi @Melissa S ,

Company-managed Project or Team-managed Project?

[Melissa S]

Neither, it's when the instance is newly setup before the creation of any projects.