Issue Type Layouts and Screen Schemes

[John Lord]

Hello,

I created a project for our RPA team. I need to create 3 different issue types called New RPA Request, New Enhancement/defect and RPA Errors. Each of these issue types needs to have a form submitted to create the jira issue in the project (I have this set up already). I want to be able to have each issue type have their own issue layout and scheme. Is this possible? The only way I can figure out how to get close to this is to have the issue field configuration to have multiple tabs and have the unique fields assigned to those tabs. I know I cannot put the same field on each tab and this is causing issues. The image below shows the three tabs I have on my issue. 

[Walter Buggenhout]

Hi @John Lord,

I noticed this question has not been addressed; you are addressing the most complex and layered part of configuring Jira projects. Let me give it a try ...

Yes, you should be able to make this work. In a company managed project, every available issue type can use its own screens. But you need quite a few steps before you are there. A couple of things to understand first:

Every issue type can use a separate screen for these operations: create / edit / view. Jira uses schemes to bundle these screens into a package that you can use to assign these screens to an issue type. These are called screen schemes.

But in a project, you obviously use more than 1 issue type. So you also need a way to associate these screens schemes to the right issue types in your project. This is done through an issue type screen scheme. And that is the thing you associate to your project.

As you have 3 issue types that you want to set up different screens for, this is what you need to do:

• Create separate screens for each issue types with just the fields you want for each issue type. Because you can create / edit / view each issue type, you may end up with 9 different screens (3 for each issue type). It is perfectly fine to re-use a screen for different operations (it is quite common to use the same screen for editing/viewing and to have a different screen to create issues with fewer fields on it)
• For each issue type, create a screen scheme that has the bespoke screens for that issue type associated with the correct operations. You should end up with 3 screen schemes, 1 for each issue type.
• Create an issue type screen scheme and link the screen schemes you created in the previous step to their respective issue types.
• Link that issue type screen scheme to your project.

At that point, each issue type in your project should be associated with its own set of screens.

Hope this helps!

[Luis Cornejo]

I am struggling with this one to. where do i associate the issue type with the screen operations?