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 multiple fields for entire project?

Tiffany Lirones_zxa38r

I am creating a Field Configuration to only show some specific fields for a new project I am creating.

Currently, the Default has way too many fields for my purpose, and I would like to simplify it down.

Is there a way to hide many, many, many fields at once, or do I need to click the Hide link for every single field, individually?

Accepted answers

All comments

Joe Pitt

If you want to hide so many fields it sounds like you are using all the fields in your project. I've stood up hundreds of projects and never needed to hide a field. When I create custom fields I restrict them to projects or issue types.

Tiffany Lirones_zxa38r

I think this is not the case in my enterprise. It seems that there are hundreds of custom fields, all assigned to the default configuration? Is there a way to create a configuration from scratch that only contains, say, five specific fields?

Joe Pitt

They will all be in the default field configuration, but they shouldn't all be assigned to all issue types. If a field isn't used in an issue you don't need to hide it.

Each issue type can have its own field configuration. Field configuration schemes are composed of one or more field configurations. Every issue type can have its own field configuration inside the field configuration scheme. If you have 5 issue types and 1 has special needs you create a field configuration for the 4 issue types and another for the 1 issue type. Then you combine them into a field configuration scheme and apply that to the project. When an issue is created, it looks for a field configuration for that issue type and uses it. If it doesn't find one it uses the default in the configuration scheme. Copy/paste this link for more information. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html

Tiffany Lirones_zxa38r

This is super complicated to me - more than I need. I am sorry I am not following completely.

I have a Project. I want this project to have 1 Issue Type (say, Task) I want my issues (Tasks) to have just 5 fields.

How do I execute this? Is there a tutorial for this somewhere?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

field

field-configuration