# Hide field options

Controls which options are visible in a field's dropdown or selection list, based on conditions. Use this to filter available choices dynamically - for example showing only relevant resolutions based on issue type, or restricting priority options by user role.

**Supported contexts:** Global Issue Create, Issue View, Issue Transition, JSM Request Create.

***

## 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.

When the rule runs and the currently selected value becomes hidden, the selection is automatically cleared. This behaviour applies on Global Issue Create, Issue Transition, and JSM Request Create. On Issue View, the selected value is not changed - only the visible options are updated.

***

## Configuration

| Option            | Description                                                                                |
| ----------------- | ------------------------------------------------------------------------------------------ |
| **Target field**  | 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.               |

***

## 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](/field-rules/rules/hide-issue-types.md) rule.

***

## Value clearing when options are hidden

When the rule hides the currently selected value, the behaviour depends on the field type and view:

When the selected value becomes hidden, it is cleared from the field. For multi-value fields, only the hidden selections are removed. Priority is an exception - it cannot be cleared, so it is switched to the first available visible option instead.

This only applies on **Global Issue Create**, **Issue Transition**, and **JSM Request Create**. On **Issue View**, the saved value is never modified.

***

## 100 options limit

On Issue View and Issue Transition, the number of options passed to `setOptionsVisibility` cannot exceed 100 per update. The option picker in the admin form enforces this limit - additional selections are disabled once 100 options are chosen.

***

## Examples

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

**Restrict priority options by role**\
Hide "Critical" and "Blocker" priorities for users with the "Developer" project 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 issue with an old version.

***

## Known limitations

* **Affects versions, Fix versions, Parent, and Resolution** are only supported on Issue Transition.
* **Issue Type** is not available in this rule - use [Hide issue types](/field-rules/rules/hide-issue-types.md) instead.
* **100 options maximum** per update on Issue View and Issue Transition.
* **Value clearing on Issue View is not supported.** The currently saved value is never automatically changed when options are hidden on Issue View.
* **JSM Request Create** only supports single select, multi select, and priority for option visibility control.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.forgappify.com/field-rules/rules/hide-field-options.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.