Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Set our server instance to READ-ONLY

  During our migration from Jira server to Jira cloud I am looking to make sure we set our server instance to READ-ONLY. What I have found through my research is to set up a permission scheme and a user group.  Then once the migration begins give all the users the group and set the permission scheme to all projects. Within the permission scheme it only has access to "Browse". 

   Are there any other ways to complete this task or is this the best process to do during this migration?

   Any and all information would be greatly appreciated.

1 answer

1 vote
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 09, 2021

Hi @Josh Barnes 

To the best of my knowledge, that's still the only workable solution for the server platform.  You may want to insure that in addition to a "browse" permission scheme, no Global Permissions need to be changed temporarily.


So the migration advice is worded poorly:  set server instance to read only.

It should be set instance user permissions to read only (using a scheme).


I have just found this out and it is a PITA to be honest as we have many schemes to be amended then re-set.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events