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
Everyone makes mistakes, and sometimes you don't know you did until after pulling the trigger.
Some migrations take a very long time to complete. How can we kill it and reset our settings and start over?
Hi @Jean Dupree ,
While @vikram is correct in reaching out to support to see what is causing the migration to take a long time.
Only Confluence has the ability to stop a migration that was started using CCMA from the UI.
Jira on the other hand does not have a stop button, not yet at least. The only way to actually stop a Jira migration that has been initiated using JCMA is to delete the plan from the database. That will actually delete the specified plan from the UI as if it never happened.
That should be something you do only after you are sure you do not need any migration logs and completed all troubleshooting, basically as last resort.
Hope this helps and let me know if you have any future migration questions.
Hi Jean Dupree
Welcome to community.
Please contact support https://support.atlassian.com/contact
Support team look from backend, what process are taking long time and kill the process if required.