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; } } }

Custom Field Values

unknown

Hi there,

We are now finding that some of our custom fields are no longer relevant or some the values are now redundant.

Is there a way to remove or hide custom field values that are no longer in use but leave the rest of the custom field as it is?

Also is there a way to hide custom fields completely?

Many Thanks

Accepted answers

Nic Brough -Adaptavist-

For select lists, you can "disable" options, which means people can't select them any more, but they remain on the issues so you can still find them. (Removing the options strips them off the issue completely)

You can use screens, field configurations or field context to hide custom fields you no longer need. Which is the best choice of those actually depends on how you're currently controlling where the fields are used.

But if you want to be very blunt and completely excise a custom field (without losing it's data), go to Admin -> Custom fields, find it in the list and change it's "context" so that it only appears in one (empty/old/unused) project.

All comments

Henning Tietgens

Fields could be hidden through the Field Configuration used by a issue type / project.

Nic Brough -Adaptavist-

Udo Brand

You can hide custom fields, just go to the field configuration in your project and hide them. Make sure that these fields aren't used in conditions or validators.

Regarding the redundant values, that is more complex. If you have AAA and aaa as values used in a select list and you want use only AAA any more, you would need to replace aaa in all issues bei AAA. This might not be possible since some of the issues are closed and can not be edited any more.

for those closed issues you would need to add a transition from closed to closed. Add a screen whith that field to that transition (with condition to admins only) and do a bulk update on those issues.

Once you have cleaned up all issues you can remove that unwanted value from the custom field configuration.

unknown

Thanks for your help! I think the 'disable' option may be the way to go forward to ensure that we are not affecting any closed issues.

Greatly appreciated!

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