Freezing Jira Cloud Projects Read-Only for Migration and Reverting Them

Jira Cloud has no built-in option to make a project read-only, so teams apply a read-only permission scheme during a migration cutover and later restore each project's original scheme. On a large site this means hundreds of separate API calls in each direction, and reverting only works if the starting schemes were recorded beforehand. The author tested the full process on a 64-project Jira Cloud test site in November 2026 using an open-source toolkit, freezing 12 projects plus one team-managed project. After reverting, a comparison of before and after exports showed all 64 projects back on their original schemes. Along the way, two errors appeared, and Jira also added 40 unexpected grants to the read-only scheme, which could let apps and automation rules still write to projects.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in