> 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/show-field.md).

# Show field: show or hide a Jira field based on conditions

Show or hide a Jira field based on another field's value, the user, their group or role, or the space and work type. Conditional fields with no scripting.

Field Rules can show or hide a Jira field based on conditions, so a field appears only when it is relevant. Control visibility using the value of another field, the current user, their group or role, or the space and work type - the building block for conditional fields and dynamic forms. Visibility updates in real time as the user fills in the screen, with no scripting and no extra screens to maintain.

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 **Show field** rule and choose the field to show or hide under **Field name**. The field must already be on the screen - the rule controls the visibility of existing fields, it cannot add new ones.
3. Add **preconditions** - field values and/or user identity - that determine when the field is visible. Without preconditions the field stays visible at all times, so the rule has no effect.
4. Save. When the screen loads or a watched field changes, the rule re-evaluates: if the conditions pass the field is shown, otherwise it is hidden.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-1b4f4b3299516dc570ea2309008a8c528551e67a%2Fshow-field-rule-reason-for-high-priority.png?alt=media" alt="Configuring a Show field rule that reveals a Reason for high priority field only when Priority is one of High or Highest"><figcaption><p>Showing a "Reason for high priority" field only when Priority is set to High or Highest.</p></figcaption></figure>

| Option            | Description                                                                                                                                                                          |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Field name**    | The field to show or hide.                                                                                                                                                           |
| **Preconditions** | Field and/or user conditions that determine when the field is visible. Preconditions are optional, but without them the rule has no effect - the field remains visible at all times. |

***

## How it works

Define the conditions under which the field should be visible. When the screen loads or the user changes a watched field, the rule re-evaluates. If conditions pass, the field is shown. If they do not, the field is hidden. With several Show field rules on the same field, the field is visible only when the conditions of all of them are met.

***

## Examples

**Justify high priority**\
Show a "Reason for high priority" field only when Priority is set to "High" or "Highest" (a field condition using the "is one of" operator), so anyone raising a high-priority work item has to explain why. The field stays hidden for every other priority.

**Progressive disclosure**\
Show a "More details" text field only when a "Needs clarification" checkbox is selected. The field stays hidden until the user signals that additional information is required.

**Role-based field visibility**\
Hide the "Internal notes" paragraph field for all users except members of the "Support Agents" group. Regular users never see the field; support agents always do.

**Reveal a field on a transition**\
On a transition screen, show a "Rollback plan" field only when "Change type" is set to "Emergency". The field appears the moment the value is chosen and hides again if it changes.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-334e02acfc4c8aa752ff12cdec3ab9c42f9153a6%2Fshow-field-on-transition.gif?alt=media" alt="On a transition screen, setting Change type to Emergency reveals the Rollback plan field; changing it to another value hides it again"><figcaption><p>Showing a "Rollback plan" field on a transition only when "Change type" is "Emergency".</p></figcaption></figure>

***

## When to use it

Use Show field when a field only matters in certain situations and cluttering the form for everyone else is the alternative. It is the right tool when the decision to display a field depends on data or identity, not just work type:

* **Reacts to another field's value** - reveal a field only after a relevant choice is made.
* **Reacts to the user** - show or hide a field based on group or role.

If a field should always appear for a given work type, Jira's own screen configuration already covers that. Reach for Show field when visibility has to react to field values, users, or roles.

***

## Doing this without Field Rules

To show a different set of fields per work type without an app, Jira's traditional approach is separate screens: map each work type to its own screen scheme and its own screen, and repeat that for every operation - Create, View, Edit - that needs to vary. If the field sets are genuinely different, that's reasonable. But if several work types differ by only a field or two, you end up duplicating an otherwise identical screen for each variant, multiplied again across every operation, and keeping every copy in sync whenever a shared field changes.

Field Schemes' "Available on" setting offers a lighter native alternative: keep one shared screen with every field on it, and for the fields that should only appear for specific work types, narrow "Available on" from "All work types" to just the ones that need it. This is effectively the same idea as the Show field rule with an Issue Type condition - one screen, fields appearing conditionally - except it's a static setting an admin configures ahead of time, not a rule.

The difference is what the condition can be based on. "Available on" only varies by work type. Show field can react to work type too, but also to the value of any other field on the screen, or to who the user is - their group, role, or identity - and it re-evaluates live as the user fills in the form. Native Jira has no equivalent for those cases.

Conditions beyond work type, and real-time reactivity, require 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.

Further reading: [How to hide fields in Jira Cloud - by work type, field value or user](https://community.atlassian.com/forums/discussion/3315528/how-to-hide-fields-in-jira-cloud-by-work-type-field-value-or-user) walks through Jira's own settings and the Show field cases they cannot cover, with an example.

***

## Supported fields

All field types [supported by the UI Modifications API](https://docs.forgappify.com/field-rules/jira-administrator/supported-fields-per-view.md) are available, with the following exceptions for the show/hide operation.

* **Issue Type, Project, Status** - not supported on any view.
* **Resolution** - only supported on Issue Transition.
* **Summary** - supported on Global Issue Create, Issue Transition and JSM Request Create, not on Issue View.
* **Due date** - only supported on Global Issue Create and JSM Request Create.
* **Components, People** - not supported on Issue Transition.
* **Original estimate** - not supported on Global Issue Create.
* **Target start, Target end** - only supported on Global Issue Create.
* **JSM Request Create** - not every field can be shown or hidden on the JSM portal. Assignee, Reporter, Components, Checkboxes, Radio buttons, Fix versions, Affects versions, and Parent are not available.

***

## Interaction with Make field required

A required field is never hidden, whether it is required in Jira or by a [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) rule. When a Make field required rule on the same field applies, the field is shown even if a Show field rule would hide it.

***

## Limitations

* **The field must be added to the screen.** The rule cannot make a field appear if it has not been added to the relevant Jira screen configuration. If the field is missing, the rule has no effect.
* **Values persist when hidden on Global Issue Create and JSM Request Create.** A value entered before the field was hidden is kept and submitted with the work item.
* **JSM Request Create has limited field support.** See [Supported fields](#supported-fields).

***

## Related rules

* [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) - make a field mandatory based on conditions.
* [Hide field options](https://docs.forgappify.com/field-rules/rules/hide-field-options.md) - filter the available options within a field.
* [Lock field](https://docs.forgappify.com/field-rules/rules/lock-field.md) - make a field read-only instead of hiding it.
* [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md) - update a field when another field changes.
