How do I stop people editing a Jira work item after it is closed or Done?

By Kayabyte · Updated 18 November 2026

Short answer: In a company-managed project, add the jira.issue.editable property with the value false to the Done or Closed status in the workflow. Work items in that status can’t be edited by anyone, for every field at once. If you want only some fields to stay as they were when the work item was closed, Jira has no setting for that. The no-code option is Lock Fields After Approval for Jira (formerly Record Lock), a Marketplace app I make: it puts the closed values back within seconds when someone changes them, and logs the attempt.

Disclosure: I make Lock Fields After Approval for Jira. The native option comes first, and the limits of both are listed below.

Option 1: the jira.issue.editable status property

  1. Go to Settings > Work items > Workflows and edit the workflow.
  2. Select the closing status (Done, Closed, Resolved) and open its properties.
  3. Add the key jira.issue.editable with the value false, then publish the workflow (Use workflow properties).

What it costs you:

Option 2: leave the field off the Edit screen

For a single field you can build a Create and View screen that include it and an Edit screen that leaves it out (Atlassian KB). The field can then be set at creation and not edited afterwards. Screens are chosen per operation and work type, not per status, so the field is also uneditable before the work item is closed.

Option 3: lock only the chosen fields when a work item is closed

Lock Fields After Approval for Jira is built for “keep this as it was when we closed it”.

  1. Install it and open its admin page.
  2. Create a lock rule: choose projects and work types, the trigger (the work item enters a status, gets a resolution, or is created, with an optional grace period) and the fields to lock.
  3. Choose Audit only (log every change) or Enforce (put the closed value back and log it). Start with Audit only.
  4. Optionally exempt a group or project role; their changes are logged and become the new locked values.

Other fields, comments, logging work and your automation keep working. Find locked work items with recordLocked = yes in JQL. It works in company-managed and team-managed projects, runs on Atlassian Forge and makes no calls outside Atlassian. Free for up to 10 users.

Limits you should know about:

Which one fits

If the whole work item should be frozen once closed and nobody needs automation or time logging on it, jira.issue.editable is simpler and stricter than my app. If only a few fields must stay as closed, the rest must stay editable, or you work in a team-managed project, the app fits better.

Not a Jira admin? Send this to yours

Only an admin can install apps. Copy this note and send it to yours:

Could we try Lock Fields After Approval for Jira? Keep approved Jira fields as they were approved. Choose the fields and a trigger. Later changes are logged and, in Enforce mode, put back. It is on the Atlassian Marketplace and built on Atlassian Forge, and it makes no calls outside Atlassian. Free for up to 10 users. Listing: https://go.kayabyte.dev/atl/record-lock?s=site-ask-jira-prevent-editing-closed-issues

FAQ

Does Jira have a “lock after Done” setting? Not as a project setting. The built-in way is the jira.issue.editable status property, company-managed projects only.

Can I still log work on a closed work item? Not with jira.issue.editable = false; logging work counts as an edit.

Can Jira Automation edit a work item in that status? No, the rule fails.

Does Lock Fields After Approval for Jira make fields read-only? No. It puts the locked value back within seconds and logs the change.

Jira and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.