Custom issue type and screens within a shared project that has defaults as well

[Louis.Seefried]

I have created a couple of new issue types (custom1 & custom 2). The new issue types will use custom fields that i do not want included within the default issue types so i created a new screen definitions (would like each to have its own screen definition since they will have different fields (custom issue 2 will leverage the general information from custom issue 1 but will have additional tabs for more information).

Can I have the custom issue types with their custom screen schemes reside in the same project that contains default issue types and schemes or do they need to be in a different project?

[Trudy P Claspill]

Hello @Louis.Seefried 

Welcome to the Atlassian community.

The short answer is yes, they can be in the same project. However, you will have to change the Issue Type Screen Scheme used by that project.

A project gets exactly one Issue Type Screen Scheme associated to it.

Within the Issue Type Screen Scheme you link Screen Schemes to Issue Types. Each Issue Type is linked to just one Screen Scheme, but you can have multiple pairing, like this:

In the above Issue Type Screen Scheme, the Bug and Sub-task issue types use the screens defined in one Screen Scheme, while all other issue types used the screens defined in "CS: Scrum Default Screen Scheme".

So, you could add the new Screens/Screen Schemes you have created for the new new Issue Types to the Issue Type Screen Scheme used by the project. If the Issue Type Screen Scheme used by the one project is used by other projects also, then you might want to copy it, change the copy, and then associate the copy to the project.

[Dick]

To keep management manageable, I would recommend sticking to a single version. With 100 people, you get 100 ways they would like their screen to be. 

just my 2 cts.

:)