Remove field from single issue type sharing screen with other issue types

Hilma Maria Tivegård April 11, 2024

I have a project where all issue types share the same screen. I want to remove a field from ONE of these issue types, without affecting the other ones. How can I achieve this?

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 11, 2024

Hello @Hilma Maria Tivegård 

You will have to create a separate screen that issue type, add that to a new Screen Scheme, and associate that new Screen Scheme to the specified issue type in the Issue Type Screen Scheme used by the project.

If the Issue Type Screen Scheme is used by multiple projects, and you want this to affect only one project, then you will also have to create a new Issue Type Screen Scheme for that one project.

If you only want to remove the field from the View/Edit screens, then you can do that by changing the Issue Layout for that one 

Hilma Maria Tivegård April 11, 2024

Hi @Trudy Claspill , thanks for the quick reply. Is there a step by step tutorial on how to do this? No matter what I do, I never get to a point where I can add a new screen scheeme to the project. 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 11, 2024

The structure is

Issue Type Screen Scheme - project gets only one of these

Issue Type Screen Scheme contains a mapping of issue types to Screen Schemes. All issue types might use the same Screen Scheme, or you may have different issue types using different Screen Schemes. An issue type can be mapped to only one Screen Scheme within the Issue Type Screen Scheme.

Screen Schemes contain Screens that are associated to Issue operations - Create, Edit, and View. In the Screen Scheme itself there is no reference to issue types.

 

Implementation is in the reverse order.

1. Create the new Screen

2. Create the new Screen Scheme

3. Update (or create a new) the Issue Type Screen Scheme

4. If you had to create a new Issue Type Screen Scheme, associate the new Issue Type Screen Scheme to the project.

 

https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/

 

Does that project currently share the Issue Type Screen Scheme with other projects? If so, do you want this change to affect only one project? 

Hilma Maria Tivegård April 15, 2024

Yes, I wanted the change to apply to all projects sharing the Issue Type Screen Scheme, so this solution worked exactly as I wanted. Thanks for the help!

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events