nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hide Affect and Fix Version and Component

K Kelly

Since Issues are a Jira generic term to use for all sorts of items (whether client request, service request, enhancement, etc), we want to create issue types for other business units besides engr/dev. However, fields like affects or fixed versions, or components are not applicable.

Why are these not options to show on a screen and is there a way for me to hide them? I've created my own screens and associated to a screen scheme and defined for the issue types - so, these customizations I have made work fine. But, I just don't want these other fields as they cause confusion in View mode, even though they cannot edit them.

Any ideas?

Accepted answers

Ramiro P

As you can create the screens and assign them to a Screen Scheme, you can create 3 types of screen per issue:

1- Create Issue Screen

2- Edit Issue Screen

3- View Issue Screen

In each one you can select which fields you will show.

All comments

Ramiro P

As you can create the screens and assign them to a Screen Scheme, you can create 3 types of screen per issue:

1- Create Issue Screen

2- Edit Issue Screen

3- View Issue Screen

In each one you can select which fields you will show.

Ramiro P

I'll recommend to create the screens, then assign them to an screen scheme, and then assign that screen scheme to an issue screen scheme. In fact, that is the way it works

Karie Kelly1

I used the same screen for all three states of create, edit, and view. However, the view always shows priority, affects version, components, and fix version even though I do not include these on my screens. I know iit is applying my scheme because my others custom fields are there and it is properly displaying for the different schemes I have for each of my four issue types.

Ramiro P

Must be something wrong inside the screen scheme... Maybe the default option... Or the mapping with the issue type... In my case I have the 3 screens for every issue type and I never had any problem.

Could you check to what screen is mapped the default inside the scheme?

K Kelly

The responses regarding setting up the screen schemes and issue type screen schemes are all correct and ones that I did.

The response provided by support was that I had to also set up a Field Configuration and then a Field Configuration scheme for my project.

I wanted to hide Priority, Affects Version, and Component. So, I created field configuration in which these fields are hidden.

Then I created a field configuration scheme and associated these issue types to that field configuration. I have one issue type that I need priority for so I'll create a separate field configuration for that.

Once I applied the field configuration scheme to my project, those fields were no longer visible in the Details section.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud