You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have created a custom field with a Select List (single choice) . I inserted some options for this Select List.
All options which exist are used in different issues. Now one or more options of this listbox are not longer valid.
This means I want to avoid that the user can select these options . But I don't want to delete them (because in this case the options are deleted from the issues).
So my problem is:
I cannot deactivate this Select List because there exist still also valid options which the user should be able to select.
Disable the options in the select list.
Go to admin -> custom fields, find the field, click configuration to get to the list of options. Next to each option, you have actions - delete, rename and disable.
Disabled options can not be selected, but remain on existing issues, and can still be searched/reported.
@Nic Brough -Adaptavist- - can you offer any advice on disabling the field in the current UI? There is seemingly no longer an obvious "disable" link. I have checked options for Custom fields, field configuration and screen configuration and cannot find anything but hide or remove.
I have a similar issue. I disabled a Custom Field type option but it continue to show up in drop down list to select and when a user sends in request, it still showing up at the top as the selected item. Anyone know how to remove it from showing up but not delete it? I don't want to delete it since it is tied to many projects/tasks. I just want to disable it so that it's not visible to users. Thank you.
If you disable/deactivate a particular value for a field as described here, can you still import that field value afterward? We are in the process of doing data migration and need particular field values to exist to do the import, but we don't want anyone to inadvertently select it in the mean time.
Yes, you can still import. And report on the deactivated values. You just can't use the values when creating new issues with the "new issue" function, or editing them into place (imports are not considered "new" issues, they're thought of as "existing somewhere else and needing to be moved into your Jira")