> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/rules/hide-field-options.md).

# Hide field options: filter dropdown options in Jira

Filter the options in a Jira dropdown or selection field based on conditions - by user, group, role, work type, or another field's value. No scripting.

Field Rules can filter the options shown in a Jira dropdown or selection field based on conditions - hiding some choices or allowing only a specific set. Restrict the available options by the current user, their group or role, the work type or request type, or the value of another field, so users only ever pick from valid choices. It works on standard Jira screens and JSM portals, with no code.

The JSM Agent views behave like their standard equivalents, so this page names only the standard views.

***

## How to set it up

1. Open the **UI Modification** for the context you want to control (space, work type, and view).
2. Add a **Hide field options** rule and choose the field under **Field name**.
3. Choose a **Mode**: "Hide selected" hides the options you list; "Hide all except" shows only the options you list.
4. Pick the **Options** to hide or allow (up to 100).
5. *(Optional)* Add **preconditions** - field values and/or user identity - so the filtering only applies when they match. Leave empty to always apply.
6. Save. When the rule runs, the field's option list is filtered accordingly.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-fd757689bd818d93c9b2dcb30dd83fcf4144aca3%2Fhide-options-rule-request-type.png?alt=media" alt="Configuring a Hide field options rule on a JSM portal that shows only Website, Mobile app, and API in the Affected area field for the Report a bug request type"><figcaption><p>Showing only the relevant "Affected area" options for the "Report a bug" request type on a JSM portal.</p></figcaption></figure>

| Option            | Description                                                                                |
| ----------------- | ------------------------------------------------------------------------------------------ |
| **Field name**    | The field whose options will be controlled.                                                |
| **Mode**          | "Hide selected" hides the chosen options; "Hide all except" shows only the chosen options. |
| **Options**       | The options to hide or allow. Up to 100 options can be selected.                           |
| **Preconditions** | Optional field and/or user conditions. Leave empty to always apply the rule.               |

***

## How it works

Configure a list of options and choose one of two modes:

* **Hide selected** - the listed options are hidden, all others remain visible.
* **Hide all except** - only the listed options are visible, all others are hidden.

***

## Value clearing when options are hidden

On **Global Issue Create**, **Issue Transition**, and **JSM Request Create**, a selected value that becomes hidden is cleared from the field. For multi-value fields, only the hidden selections are removed. Priority can't be cleared, so it is switched to the first visible option instead. On **Issue View**, the saved value is never changed.

Only a value already selected when the rule runs is cleared. Place Hide field options after any Pre-fill field or Change field value rules on the same field, see [Multiple rules on the same field](https://docs.forgappify.com/field-rules/jira-administrator/execution-order.md#multiple-rules-on-the-same-field).

***

## Examples

**Filter options by request type on the JSM portal**\
On a Jira Service Management portal, show only the relevant "Affected area" options for each request type. Use Mode "Hide all except", list the areas that apply (for example Website, Mobile app, API), and add a precondition on Request Type. Add one rule per request type in the same UIM to branch the option list.

**Filter resolutions by work type**\
On the Issue Transition screen, show only "Fixed" and "Cannot reproduce" resolutions when the Issue Type is "Bug". For other work types, show the full resolution list.

**Restrict priority options by role**\
Hide "Critical" and "Blocker" priorities for users with the "Developer" role. Only team leads and above can set those priority levels.

**Dynamic checkbox filtering**\
When a "Confirmed" checkbox option is selected, hide the "Needs investigation" option. This prevents contradictory selections in the same checkbox field.

**Limit fix versions on transition**\
On a "Release" transition screen, show only the current active fix version and hide all past versions. This prevents accidentally stamping a resolved work item with an old version.

***

## When to use it

Use Hide field options to keep dropdowns free of invalid or irrelevant choices:

* **By role or group** - hide high-impact options (such as Critical or Blocker priority) from users who should not set them.
* **By work type** - show only the resolutions or versions that make sense for the current work type.
* **By another field's value** - narrow one field's options based on an earlier selection, for dependent dropdowns.

Use "Hide all except" when it is easier to list what should remain; use "Hide selected" when you only need to remove a few options.

***

## Doing this without Field Rules

Standard Jira Cloud controls a field's available options through field contexts, and a single field can have several contexts - each scoped to specific spaces and/or work types, each with its own set of available options. That's the native way to give a dropdown a different option list depending on where it's used.

The catch is that each context needs its own, largely duplicate option list. If only a couple of options differ between work types, you still maintain a near-identical list in every context, and a change to a shared option has to be repeated across all of them - the lists drift out of sync over time. Field Rules filters one shared option list with conditions instead, so there is no context to duplicate and nothing to keep in sync.

More fundamentally, contexts are scoped to spaces and work types only - they cannot vary by who the user is or by the value of another field on the screen. There is no native workaround for that: filtering options by user, role, or another field's value requires a UI Modifications app like Field Rules or a scripting app. Field Rules closes this gap with a no-code, visually configured rule - no developer required.

See [Field Rules vs native Jira](https://docs.forgappify.com/field-rules/jira-administrator/field-rules-vs-native-jira.md) for the full comparison across every rule.

***

## Supported fields

| Field type       | Global Issue Create | Issue View | Issue Transition | JSM Request Create |
| ---------------- | ------------------- | ---------- | ---------------- | ------------------ |
| Checkboxes       | Yes                 | Yes        | Yes              | No                 |
| Single select    | Yes                 | Yes        | Yes              | Yes                |
| Multi select     | Yes                 | Yes        | Yes              | Yes                |
| Radio buttons    | Yes                 | Yes        | Yes              | No                 |
| Priority         | Yes                 | Yes        | Yes              | Yes                |
| Affects versions | No                  | No         | Yes              | No                 |
| Fix versions     | No                  | No         | Yes              | No                 |
| Parent           | No                  | No         | Yes              | No                 |
| Resolution       | No                  | No         | Yes              | No                 |

To control Issue Type options, use the dedicated [Hide issue types](https://docs.forgappify.com/field-rules/rules/hide-issue-types.md) rule.

***

## Limitations

* **Up to 100 options per rule.**
* **Value clearing on Issue View is not supported.** The currently saved value is never automatically changed when options are hidden on Issue View.

***

## Related rules

* [Hide issue types](https://docs.forgappify.com/field-rules/rules/hide-issue-types.md) - control which work types are available on Create and Transition screens.
* [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md) - set a field's value when another field changes; pairs with option filtering for dependent dropdowns.
* [Show field](https://docs.forgappify.com/field-rules/rules/show-field.md) - show or hide the whole field rather than individual options.
* [Lock field](https://docs.forgappify.com/field-rules/rules/lock-field.md) - make a field read-only.
