Issue Types with their own Scheme

[Jeff Murray]

Hello -

As I'm taking over the Jira admin for our scrum projects, I've noticed some of the projects share a scheme, others their own.

The goal is to 1) have each issue type with their own scheme 2) Share each issue type along all scrum projects.

What is the best way to reconfigure this goal?

Thanks,

Jeff

[Rebekka Heilmann _viadee_]

Hi @Jeff Murray 

I don't quite understand what you mean with "each issue type with their own scheme". What do you want to configure per Issue Type? Screens? Workflows?

There is not just one "scheme" in Jira. Schemes are used to associate one configuration object with others. Screen schemes, Issue Type screen schemes, workflow schemes... and so on. 

For sharing a specific set of issue types between projects you need to configure an Issue Type Scheme and use that for all the projects.

[Mikael Sandberg]

Just to add to @Rebekka Heilmann _viadee_ answer, here is a good reference to see how all the schemes are linked together. The KB is for Data Center, but it works the same on Cloud.

[Jeff Murray]

I want to have separate screens per issue type to control the field layout. If we add / remove a field, it should only effect the one type, not others. Workflows would be the same. 

Mikael - thanks for the reference. 

[Nic Brough -Adaptavist-]

That is what "issue type screen schemes" are for, not "issue type schemes".  You'll need to create an issue type scene scheme for each project to tell a project what "screen scheme" you want to use for each issue type. 

The screen schemes then tell the project what screens (which are not anything more than a list of fields to show) for create, edit, and view.