How to make Jira issues read-only using workflow properties

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Various workflow properties implement restrictions on certain steps or transitions of workflows which can be used to prevent modifying Jira issues once they reach a certain status ( such as Closed )

The following workflow properties will prevent issues from being linked, moved, commented on, or deleted:

Property

Value

jira.issue.editable

false

jira.permission.link.denied

true

jira.permission.move.denied

true

jira.permission.comment.denied

true

jira.permission.delete.denied

true

jira.permission.bulkchange.denied

true

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.