Select list options

The problem. Adding one option to a select list is a Jira administrator task. That is why a request as small as “please add our new vendor to the dropdown” sits in a queue for a week.

What this does. Moves that one specific job to the people who own the process, and nothing else. The project admin cannot change the field, its contexts, its screens or its type.

Step 1 — a Jira admin enables the field

1. 1Make sure the field has a field context limited to one project. Create one in *Settings → Issues → Custom fields → field → Contexts* if needed.
2. 2Open Jira → Apps → Custom Fields Toolkit → Select List Option Management.
3. 3Find the field and context in the table and switch Delegate on.

Four field types can be delegated, not only the two the name suggests: Select List (single), Select List (multiple), Checkboxes and Radio Buttons. They all hold a list of options and they are all edited the same way.

The table is searchable and paginated, and Only fields with a delegable context filters it down by probing each field's contexts — it reports progress as it goes, because on a site with thousands of custom fields that check takes a moment. Each row links straight out to the field's and the context's own Jira configuration screens.

Step 2 — the project admin manages the options

• The page is at Project settings → Select List Options, and lists only the fields delegated for that project. If none are, it says a Jira administrator has to enable one first.
• Add Option adds a value. Click a value to rename it. Delete removes it after a confirmation that says the action cannot be undone.
• An option can be switched from Enabled to Disabled instead of deleted. Disabling keeps it on the issues that already use it, while removing it from the dropdown for new work.
• Move up and Move down reorder the list, which is the order users see in the dropdown. Long lists are paginated.