How to make Jira issues read-only using workflow properties
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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 |
Last modified on Jun 3, 2021
Powered by Confluence and Scroll Viewport.