> 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/jira-administrator/field-rules-vs-native-jira.md).

# Field Rules vs native Jira: what each one does

Jira configures fields per work type. Field Rules adds conditions: show, hide, require, lock, filter options and pre-fill by user, role or field value.

Standard Jira Cloud configures fields per work type: it can hide a field, require it, or set its options the same way for everyone. Screens, Field Schemes, field contexts, and permission schemes are global controls that apply to every user and every work item that matches their scope. Field Rules adds conditions on top - fields that show, hide, become required or read-only, filter their options or pre-fill based on who is viewing the screen, the value of another field, or the transition being performed - configured once and run across the spaces and views you choose.

{% hint style="info" %}
New here? [Conditional fields in Jira - without scripting](https://community.atlassian.com/forums/discussion/3269330/conditional-fields-in-jira-without-scripting) is a friendly, example-led introduction to everything on this page.
{% endhint %}

***

## What native Jira controls

Four mechanisms control fields in standard Jira Cloud, and each one is static and scoped, not conditional:

**Screens** decide which fields appear on Create, Edit, and Transition. A field must be added to the screen assigned to a work type before it can appear there at all.

**Field Schemes** (the modern, unified experience that replaces the older Field Configurations and Field Configuration Schemes) control three things per field, per work type, all from one place: whether it is available at all - a master switch that removes the field from every screen for that work type, across every space using the scheme, if turned off - whether it is required (none, all, selected, or all except selected work types), and its description (a rich text override). All three are configured once per scheme and apply the same way to every space that uses it. Work type is the only dimension any of them vary on - none of them vary by user, role, group, or another field's value.

**Field contexts** decide which options are available for a field, and can scope options to specific spaces or work types - but not to specific users, and not based on another field's value.

**Permission schemes** decide who can perform actions (create, edit, transition, assign), not which fields they see or can edit. There are no field-level permissions in Jira Cloud.

***

## What conditions add

Native configuration varies by work type. Field Rules adds conditions that native settings do not cover:

* Show or hide a field based on who is viewing the work item - role, group, or specific user
* Make a field required only for specific users or roles
* Lock a field (read-only) for some users but editable for others
* Show or hide a field based on the value of another field
* Filter the options of one field based on the value of another field
* Pre-fill or change a field's value based on another field or a condition

These are the situations where a UI Modifications app like Field Rules, or a scripting app, is used.

***

## Capability comparison

| Capability                                                    | Native Jira                                                                                                                                | Field Rules                                                                                                                                                         |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Show or hide a field by role, group, or another field's value | Per work type only (Field Scheme's "Available on") - not per user, role, or field value                                                    | [Show field](https://docs.forgappify.com/field-rules/rules/show-field.md)                                                                                           |
| Require a field only in certain situations                    | Per work type only (Field Scheme's "Required on") - not per user, role, or field value                                                     | [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md)                                                                         |
| Make a field read-only for some users but not others          | No - no field-level permissions exist                                                                                                      | [Lock field](https://docs.forgappify.com/field-rules/rules/lock-field.md), including on transitions and the JSM customer portal                                     |
| Filter a field's dropdown options by condition                | Per work type only (field context) - not per user or field value                                                                           | [Hide field options](https://docs.forgappify.com/field-rules/rules/hide-field-options.md)                                                                           |
| Require a field only on one transition                        | A workflow validator per transition. It checks that the field is not empty on submit and does not mark the field as required on the screen | [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) with a transition condition, shown as required on the transition screen |
| Restrict which work types can be created, by user or role     | No - work type schemes are static and space-wide                                                                                           | [Hide issue types](https://docs.forgappify.com/field-rules/rules/hide-issue-types.md)                                                                               |
| Change a field's label by condition                           | One global field name. On the JSM portal, a display name set per request type                                                              | [Use name](https://docs.forgappify.com/field-rules/rules/use-name.md)                                                                                               |
| Apply the same logic across many spaces and views             | Configuration is per scheme, per space or per field context                                                                                | One set of rules across the spaces, work types and views you choose, including team-managed spaces                                                                  |
| Pre-fill a field's value on load, conditionally               | Static default only - not conditional, not on transition screens                                                                           | [Pre-fill field](https://docs.forgappify.com/field-rules/rules/pre-fill-field.md)                                                                                   |
| Update a field automatically when another field changes       | No native mechanism                                                                                                                        | [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md)                                                                           |
| Restrict assignment to self only                              | No - the "Assign Issues" permission is all-or-nothing                                                                                      | [Enable self-assignment only](https://docs.forgappify.com/field-rules/rules/enable-self-assignment-only.md)                                                         |
| Show different hint text based on conditions                  | Per work type only (Field Scheme's description override) - not per user, role, or field value, and fixed rather than reactive              | [Use description](https://docs.forgappify.com/field-rules/rules/use-description.md)                                                                                 |

***

## Field Rules vs a scripting app

A scripting app can also achieve most of the above - Field Rules is not the only way to add conditions. The difference is how you get there: a scripting app requires writing and maintaining code, usually with a developer's help, to express each rule. Field Rules configures the same conditional logic through the admin UI - no coding knowledge, no custom scripts to maintain, nothing else to install - and one set of rules can cover many spaces and views.

***

## When native Jira is enough

Not every situation needs conditional logic. If a field should always be visible, required, or carry a specific description for an entire work type, with no exceptions by user, role, or another field's value, a Field Scheme alone is enough - there's no need to add a rule for something a global setting already covers. Reach for Field Rules when the field needs to change based on who is looking, what they've already entered, or another condition that a global Jira setting cannot express.

***

## Getting started

See the [Setup guide](https://docs.forgappify.com/field-rules/jira-administrator/setup-guide.md) to install Field Rules and create your first UI Modification, or jump directly to a rule: [Show field](https://docs.forgappify.com/field-rules/rules/show-field.md), [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md), [Lock field](https://docs.forgappify.com/field-rules/rules/lock-field.md), [Pre-fill field](https://docs.forgappify.com/field-rules/rules/pre-fill-field.md), [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md), [Hide field options](https://docs.forgappify.com/field-rules/rules/hide-field-options.md), [Hide issue types](https://docs.forgappify.com/field-rules/rules/hide-issue-types.md), [Enable self-assignment only](https://docs.forgappify.com/field-rules/rules/enable-self-assignment-only.md), [Use description](https://docs.forgappify.com/field-rules/rules/use-description.md), or [Use name](https://docs.forgappify.com/field-rules/rules/use-name.md).
