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

# Lock field: make a Jira field read-only

Make a Jira field read-only based on status, user, group, or role, so users see its value but cannot edit it. Works in Jira and JSM portals, no scripting.

Field Rules can make a supported Jira field read-only so users can see its value but cannot change it. Lock a field based on work item status, the current user, their group or role, or the value of another field - Jira's equivalent of a conditional read-only or non-editable field, configured with no scripting and no workflow changes. Optionally, override the field's description to explain why editing is disabled.

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 **Lock field** rule and choose the field to lock under **Field name**.
3. *(Optional)* Add **preconditions** - field values and/or user identity - so the field locks only when they match. Leave preconditions empty to always lock the field.
4. *(Optional)* Set a **Description** override to explain to users why the field cannot be edited. It supports basic wiki markup (bold, links, color); see [Formatting the description](https://docs.forgappify.com/field-rules/rules/use-description.md#formatting-the-description).
5. Save. The field becomes read-only when the screen loads and its preconditions pass, and editable again if they stop being met.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-06f825e02d8678e49d6fa5bbbc10b78045ca27f9%2Flock-field-rule-fix-versions-locked-for-developers.png?alt=media" alt="Configuring a Lock field rule that makes Fix Version read-only for the Developer role, with a description explaining the field is managed by the release team"><figcaption><p>Locking Fix Version for the Developer role, with a description that explains why it cannot be edited.</p></figcaption></figure>

| Option            | Description                                                                                                        |
| ----------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Field name**    | The field to lock.                                                                                                 |
| **Description**   | Optional override for the field's description text. Useful for explaining to users why the field cannot be edited. |
| **Preconditions** | Optional field and/or user conditions. Leave empty to always lock the field.                                       |

***

## How it works

When the screen loads and the configured preconditions pass, the field is set to read-only. If preconditions stop being met (for example, because the user changes a watched field), the field becomes editable again.

If the field is already read-only, for example because it is not on the Edit screen, the rule still shows its description. When the conditions stop being met, the field stays read-only and gets its original description back.

***

## Examples

* **Lock a field for non-release managers**\
  Lock the "Affects Versions" field for all users except members of the "Release Managers" group. Add a user condition set to "Except" and select the group. All other users will see the field as read-only.
* **Lock a field based on status**\
  Lock the "Fix Version" field when the work item status is one of "In Review" or "Done". Use a field condition on the Status field. Combine with a description override: "Fix version is locked once the work item is in review."
* **Lock a field for a specific role**\
  Lock the "Priority" field for users with the "Developer" role. Developers can see the priority but only project managers and above can change it.
* **Lock a field with a pre-filled default**\
  On Global Issue Create, pre-fill the "Environment" field with "Production" using the [Pre-fill field](https://docs.forgappify.com/field-rules/rules/pre-fill-field.md) rule, then lock it so users cannot change it. This ensures all work items are created with the correct environment without relying on users to fill it in.

***

## When to use it

Use Lock field when a value must stay visible for context but should only be changed by certain people or at certain stages. Common cases:

* **Ownership boundaries** - releases, billing, or account fields that only one team should edit.
* **Post-triage freezes** - lock "Severity" or "Priority" once a work item moves past triage so it is not changed mid-flight.
* **Automation-managed fields** - fields set by a rule or integration that users should not override.

***

## Doing this without Field Rules

Standard Jira Cloud has no field-level permissions and no way to make a field read-only for some users but editable for others. Field configurations mark a field required, optional, or hidden for everyone on the scheme, and permission schemes control actions (create, edit, transition) rather than individual fields. The only native option is leaving the field off the Edit screen, which shows it read-only on the work item view. It works only there, applies to everyone regardless of role or context, and not for every field: Assignee, for example, stays editable.

Conditional, role-aware read-only behaviour 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

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 lock operation.

* **Issue Type, Project, Status** - not supported on any view.
* **Resolution** - only supported on Issue Transition.
* **Due date** - not supported on Issue View and Issue Transition.
* **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 locked on the JSM portal. Assignee, Reporter, Components, Checkboxes, Radio buttons, Fix versions, Affects versions, and Parent are not available.

***

## Empty fields on Issue View

On Issue View, Jira automatically hides fields that have no value and are set to read-only. This matches Jira's default behaviour when a user lacks edit permission for a field. It is a platform behaviour and not configurable.

If you need the field to remain visible even when empty, ensure the field has a value - for example by using the [Pre-fill field](https://docs.forgappify.com/field-rules/rules/pre-fill-field.md) rule.

***

## Limitations

* **Empty fields are hidden on Issue View.** A locked field with no value is not shown.
* **No description for Description and Priority on Issue View.** These fields are locked there, but the rule's description isn't shown.
* **JSM Request Create has limited field support.** See [Supported fields](#supported-fields).

***

## Related rules

* [Pre-fill field](https://docs.forgappify.com/field-rules/rules/pre-fill-field.md) - set a value, then lock it so users cannot change it.
* [Show field](https://docs.forgappify.com/field-rules/rules/show-field.md) - show or hide a field based on conditions.
* [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) - make a field mandatory based on conditions.
* [Use description](https://docs.forgappify.com/field-rules/rules/use-description.md) - change a field's hint text based on conditions.
