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
- Go to Settings > Work items > Workflows and edit the workflow.
- Select the closing status (Done, Closed, Resolved) and open its properties.
- Add the key
jira.issue.editablewith the valuefalse, then publish the workflow (Use workflow properties).
What it costs you:
- Everything is locked, not chosen fields. Logging work counts as an edit too (Atlassian KB), and bulk edit no longer offers custom fields for those work items (Atlassian KB).
- Your own automation fails on those work items. Automation rules can’t edit their fields (Atlassian KB), and other status properties that grant permissions don’t override it (JRACLOUD-63580).
- Company-managed projects only. Team-managed projects have no way to restrict editing by status (JRACLOUD-87543).
- Admins and apps can override it through the REST API’s edit call (
overrideEditableFlag, for people with the Administer Jira permission and for apps; Jira REST API: Edit issue). - Reopen it and it is editable again, with no record of what the closed values were.
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”.
- Install it and open its admin page.
- 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.
- Choose Audit only (log every change) or Enforce (put the closed value back and log it). Start with Audit only.
- 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:
- It reverts, it doesn’t block. The field is not read-only: the change and the put-back both appear in the work item’s history.
- Rapid changes get through. To stop an automation rule and the app undoing each other forever, it gives up within 10 minutes on the same field of the same work item: the 6th change by an app or Jira Automation, or the 21st by a person, stays put.
- A project admin can switch it off by deleting the project setting enforcement relies on, until a Jira admin opens the app’s admin page or its weekly check repairs it.
- Some fields can’t be locked: cascading selects, sprint, parent, time tracking, attachments, comments and links.
- Without an active license nothing is put back or logged; the audit log and exports stay readable.
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.
More guides
- Atlassian Connect end of support: what Jira and Confluence admins should check before 31 January 2027
- How to delete old page versions in Confluence Cloud
- Apps to make a Confluence group watch a space or page, compared
- How to make a Confluence group watch a space or page
- Can you limit how many page versions Confluence Cloud keeps?
- Onboarding in Confluence: make new hires watch the right spaces automatically
- Confluence storage almost full? What counts and how to free it
- Apps to delete old Confluence page versions, compared
- Confluence watching but no email? 5 things to check
- How to track billable and non-billable hours in Jira
- How to calculate budget burn rate and run-out date in Jira
- Jira business days apps compared: JQL, Automation and holidays
- How to count business days between two dates in Jira
- How to see what a Jira epic costs from worklogs
- How to set a Jira due date N business days ahead (skip weekends and holidays)
- How to export Jira worklogs to Excel or CSV
- How do I make a Jira field read-only after approval?
- How to handle hourly rate changes in Jira cost reports without changing past costs
- How to track project cost in Jira without showing everyone hourly rates
- Can Jira stop one person from having too many work items?
- Jira project cost and budget apps compared: Tempo Financial Manager alternatives
- How to track project cost and budgets in Jira from worklogs
- How to see project cost from Tempo worklogs in Jira
- How to set a WIP limit per person in Jira
- How to see workload per assignee in Jira
- How to invoice Jira worklogs in Fiken
- How to invoice Jira worklogs in Fortnox
- How to invoice Jira worklogs in PowerOffice Go
- How to invoice Jira worklogs in Tripletex
- JQL with business days: find Jira work due within N working days
- How can I add a whole group as request participants in JSM?
- How to add a new team member to open Jira Service Management requests as a participant
- JSM agent can’t find a customer in Request participants: what to check
- Add or remove request participants with Jira Automation
- CC a whole team on every Jira Service Management request
- Why can’t a customer see a JSM request shared with their group or organization?
- Group request participants apps for Jira Service Management compared
- How to calculate on-call pay from Jira Service Management schedules
- JSM organizations vs request participants: which to use
- Why adding request participants in bulk floods inboxes in Jira Service Management, and how to avoid it
- Stop agents or the reporter ending up as request participants
- How to add public holidays to a JSM SLA calendar
- Kanban WIP limit per person in Jira: beyond column limits
- Kayabyte apps for Jira and Confluence: what each one does
- What happens to your worklogs when you leave Tempo Timesheets (Jira Cloud)
- Opsgenie to Jira Service Management: on-call pay reports
- Purge Versions for Confluence after moving to Cloud: what replaces it