Prevent all project edits with a read-only permission scheme in Jira
Platform Notice: Cloud and Data Center - This article applies equally to both cloud 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
There are times when a project no longer needs to be modified and needs to be retained for historical purposes.
This article will outline how to apply a permission scheme that will make a project browsable but not modifiable.
Solution
Create a new (blank) permission scheme
To make a project read-only, we'll need to create a permission scheme that allows it to be viewed but not modified.
Navigate to ⚙️Settings > Issues > Permission Schemes
Add Permission Scheme
Set the name as something descriptive and memorable
Select the Permissions action for the newly created permission scheme
Select Update for Browse Projects permission, and add the appropriate users or groups
If changes to any work items inside the project must be made, you may want to add additional permissions to the appropriate Admins while ensuring other users or groups don't have permission to modify issues.
Associate the newly-created permission scheme with your project(s)
Navigate to a project you want to make read-only
Select Project Settings > Permissions
Select ⚙️Actions > Use a different scheme
Set the scheme to the newly created read-only permissions scheme, then select Associate
Now the project will effectively be read-only for the selected users/groups.
For more on Project Permissions, please read Managing Project Permissions.
Looking for a method to prevent users from logging in?
Alternatively, if you're looking for a method to prevent your users from logging in during a maintenance period or want to temporarily "lock" your Jira instance with an easily reversible method, follow this guide:
Was this helpful?