Because of that it wont let me set up fields differently for each issue type.
Perhaps a video tutorial will make it clearer for you. Here is a video from the Jira guy dude buddy:
https://www.youtube.com/watch?v=sO_kaGzcJ8Y
1. Create your Screen from the /jira/settings/issues/screens location.
2. Create a Screen scheme.
3. Add issue type screen scheme OR edit the one in use by your project.
4. Edit each issue type to use different scheme as per your requirements.
Hello @Nissim Ariel
Welcome to the Atlassian community.
First can you please confirm the Type of the project you are using? Get that information by going to the Projects menu, selecting View All Projects, find your project in the list, and tell us what information is shown in the Type column.
Assuming you are using a Company Managed project, the reference material is found here:
https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-type-screens/
A project has an Issue Types Screen Scheme associated to it.
In an Issue Type Screen Scheme, issue types are associated to a Screen Scheme. Each issue type can be associated to only one Screen Scheme within an Issue Type Screen Scheme. In the Issue Type Screen Scheme you select a Screen Scheme to be used as the Default for all issue types. You can then also override that by mapping specific issue types to specific Screen Schemes.
So, to have different Screen Schemes for the issue types in a project you need to change the Issue Type Screen Scheme associated with that project.
Note that if that Issue Type Screen Scheme is associated to multiple projects, all those projects will be affected.
Hi @Nissim Ariel ,
Welcome to the Community! Have you checked this article (for company managed projects)?
Under Jira Settings-> Issues-> Issue Type Screen Schemes-> Select your screen scheme-> (...)Configure-> Associate an issue type with a screen scheme
The Screen Scheme allows to configure different screens per operation (create, view, edit)
Hi Im using company managed scrum, and when I try to associate screen scheme - Jira wants to migrate all the issue types that exist in the projects to that screen scheme. I cant manage to use more than one screen scheme to my project.
Can you tell us the exact steps you are executing, and provide screen images for each step to help us understand the process you are going through.
When you open the Issue Type Screen Scheme for the project, how many projects are associated to it?
Is this where you are trying to make your change?
Or are you in the Project Settings? And trying to associate a different Issue Type Screen Scheme with the project?
After going step by step of Jira Docs - 1. creating screen for the desired issue type on Screens - by selecting required fields, 2. creating screen scheme and relating the screen to it. 3. Issue type screen scheme - Relating an issue type - All that process in Jira Settings, then I go back to the project and look for a way to add a new screen scheme to it, and I dont have it - only use different or edit existing. I realy dont know what to do.Now I. broke it down to use only Epics. I cant find a way for other issue types we have to use. in simple way - use a different scheme - override the project with new issue type and I stay in the same status.
For each field you want to use in a project you will:
This is a multi step operation and you will only have visual exposure of each step.
So figuring out what field is used in what projects and how can be challenging.
If you are open to using apps, you can use Fields Dashboard for Jira, an app released by our company.
https://marketplace.atlassian.com/apps/1235965/fields-dashboard-for-jira?hosting=cloud&tab=overview
You will be able to see in a table how the fields are related to projects, navigate to each artifact (screen, screen scheme, issue type screen scheme, project) and export your data in csv format for storage and further analysis.
It looks like you're new here. Sign in or register to get started.
![Photo of Petru Simion [Simitech Ltd.]](https://us.v-cdn.net/6038660/uploads/avatars/c7/df/nc7dfc3cdcefb50b8aef7269c429d3d29.png)
