We are planning to migrate two instances of Jira into one. We need to make the old instance "read-only" to ensure that individuals are not adding issues to the old instance. Besides creating a permission scheme and applying it to every single project, is there a way to bulk do this to all projects?
Hi @RG
There is no built-in solution to bulk change permission scheme. There is an open ticket JRASERVER-37941, you can vote and watch. However, you can use scripts, take a look at this thread: How to Bulk Change Permission Schemes?
Also, check the answers here: Fastest way to make JIRA read only?
Keep in mind though, that if a Permission Scheme is not attached to a project, I'm not sure it's actually getting migrated to the other system. You should at least test it out with a few test projects to make sure... Otherwise you end up with projects on the other system, without the permission schemes there.
In a recent DC>Cloud migration we moved everything to one read-only scheme, and since most of the scheme couldn't be used in Cloud anyway (different groups, etc), we just ditched the old PSs and moved most projects into 2 or 3 permission schemes that were cloud-compatible with our setup there.
Things to consider/test for sure!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.