You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When migrating Jira Service Desk to cloud using the migration assistant tool, will the the original SD and portals be accessible and useable during the migration?
- Performance degradation?
- Access Issues?
- response times.
(Our servers are scalable and are of a generous specification).
Hi @Matt Smith , you don't want to have Jira "active" while migrating to Cloud via JCMA.
Any changes in issues in projects that are in scope during the migration might result in errors or the migration becoming stuck.
I would advise to avoid this and setting your Server to "read-only" as described in one of the migration steps.
Yes, indeed. Unfortunately, there is no simple toggle to set Server read-only.
Also, please note that if the active permission schemes are no longer associated with their respective project(s), they won't be migrated to Cloud!
In my case, I had to create dummy projects and link them to those permission schemes in order to migrate the permission schemes as well.
I wish Atlassian would reconsider this and find a more practical solution.
Thanks again Dave,
Another Quick question:
As long as there are no interactions with the "prod" (origin) db while the migration happens then this would be as effective as making permissions "read only".
We are thinking to make the URL accessible by the range that Jira cloud would ustilise