Jira Cloud cannot hide fields dynamically. An admin can only remove a field from a work type (issue type) in the setup, and the result is the same for everyone. To hide a field based on another field's value or the user's group or role, you need an app. Field Rules does it with conditional rules and no scripting.
Remove a field from a work type in Jira's settings
In a company-managed space, two settings decide whether a field appears:
- Screens. Each work type gets its screens through a screen scheme. The scheme has a default screen, and an admin can map Create, Edit or View to a different one. A field appears only if it is on the screen used for that operation. To remove it for one work type or operation, assign a screen without the field.
- Field Scheme "Available on". In the Field Scheme, open the field's Actions menu and choose "Change field behaviour by work type". Narrow Available on from "All work types" to the work types that need the field. The field stays on the shared screen but no longer appears for the excluded work types.
"Available on" is the lighter option, because all work types can share one screen. Both settings vary only by work type, and both apply to every space that uses the scheme. Both are fixed settings: they do not change with the values on the screen or with the person viewing it.
In a team-managed space, each work type has its own layout under Space settings > Work types. Remove the field from that work type's layout, and other work types keep it. The same layout is used on the Create screen and on the work item view, so the two cannot differ.
Hide a field based on another field's value
With a Show field rule, a field appears only when a condition on another field is met, and hides again when it is not. Example: on a Bug, show "Affected customers" only when the "Found in" single-select is "Production". The rule re-evaluates as the user fills in the form.
Show field never hides a required field, because users could not fill it in and the work item could not be saved. Use it on optional fields. To make it mandatory only when it shows, add a Make field required rule with the same precondition. For Production the field is then shown and required; otherwise it is hidden and optional.
Hide fields from specific users, groups or roles
Jira Cloud has no field-level permissions. Space permissions control what a user can do with a work item, not which fields they see.
A Show field rule with a user condition shows a field only to specific users, groups or project roles. Example: show "Internal cost" only to members of the "Finance" group.
Field Rules hides the field on the screen only, and it is not field-level security. Anyone who can view the work item can still see the value elsewhere, for example in search results, exports and the REST API. Use it to keep forms focused, not to protect confidential data.
Hide a field in one space only
Company-managed spaces often share one Field Scheme. Narrowing "Available on" affects all of them. Without an app, an admin copies the scheme for that one space, then keeps the copy in sync with the original by hand.
Field Rules can hide a field in one space only. Example: a shared "Release notes" field should not appear on Bugs in the Internal Tools space, which has no public releases.
- Create a UI Modification, a group of rules scoped to the spaces, work types and views you choose. Set:
- Project: Internal Tools
- Issue types: all
- View types: the views where the field appears, such as Global Issue Create and Issue View
- Add a Show field rule for "Release notes".
- Add the precondition Issue Type does not equal Bug.
Show field shows the field only when its precondition passes. On Bugs the precondition fails, so the field stays hidden, and other spaces are not affected.
Field Schemes, screens and layouts vs Field Rules
| Built into Jira | Field Rules |
|---|
Hide a field for a work type | Removed in the setup, fixed | Hidden by a rule, which can also depend on conditions |
Hide it in one space that shares a scheme (company-managed) | Only with a separate scheme | Yes, the rule is scoped to that space |
Hide it based on another field's value | No | Yes, live as the form is filled in |
Hide it based on user, group or role | No | Yes |
Jira's screens, Field Schemes and layouts already handle fields that should never appear for a work type. Field Rules covers the cases where visibility depends on the space, the data on the screen, or the person using it.
Field Rules hides fields on:
- the Create screen and the work item view, in company-managed and team-managed Jira Software spaces
- transition screens, in company-managed Jira Software spaces
- the customer portal and agent views, in Jira Service Management spaces
Field Rules is free for teams of 10 users or less, with a 30-day trial for larger teams: Field Rules - UI Modifications for Jira.
Follow-up: Conditional fields in Jira - without scripting shows more patterns: branching one form into different field sets, filtering options based on another field, and locking fields by role.
