-
Suggestion
-
Resolution: Unresolved
-
None
-
343
-
Issue Summary
When using Jira Cloud Migration Assistant to migrate the projects and there's a project stuck in the import, please DO NOT do anything (or delete the plan from database).
This is because deleting the plan from the Server will not stop the import process on Cloud. Thus, the new plan will not be processed while the old plan (on Cloud) is still running.
- Atlassian support has to be reached and support will have to escalate the ticket to Dev so that they can kill the import process on their end.
Workaround (Obsolete)
Stop Jira to stop plansRemove the Plan from JCMA via database: How to remove a JCMA migration plan from the dashboardRestart Jira
- is duplicated by
-
- Closed
-
- Gathering Interest
- causes
-
MOVE-95809 You do not have permission to view this issue
- depended on by
-
MOVE-57915 You do not have permission to view this issue
- is caused by
-
- Mentioned in
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- relates to
-
[MIG-187] A feature to stop a migration that has been triggered from the Jira Cloud Migration Assistant
as of JCMA 1.10.18 the following workaround worked for me:
i wanted to abort a migration which had just started (checks running)
i restarted the service and the migration had the status failed after the restart.
Could you please update solution page because its missing ? https://confluence.atlassian.com/cloudkb/how-to-remove-a-jcma-migration-plan-from-the-dashboard-1102612305.html
The above link is broken: How to remove a JCMA migration plan from the dashboard
How do I remove from the dashboard?
For anyone wondering, MOVE tickets are not visible to others unless explicitly shared.
Are there any updates? The ability to halt a migration in progress is critical functionality. If nothing else the JCMA should display a warning before running.
I've JCMA 1.6.8 get stuck on App Data migration twice now, and raised this with the App developers. Strange that event restarting Jira Server doesn't stop or abort the JCMA plan.
That's true. I had the same issue and got in touch with Atlassian and they sent me a documentation https://confluence.atlassian.com/cloudkb/how-to-remove-a-jcma-migration-plan-from-the-dashboard-1102612305.html on how the long running job could be removed from the migration plan.
As you mentioned, I was able to run another migration even if the previous migration was showing as still running.
yeah, you would have thought adding a stop button was a pretty obvious thing to have from the off.
I started the migration of about 20GB and 10k users. But I think there was a disk space issue that caused Jira to crash. On the restart, it continued for days and days without doing anything.
But one thing I realised is that I could start another migration which did complete. This might seem obvious to others but it wasn't to me.
Well this is frightening to see when I'm looking at migrating ~17,000 users and over 1000 projects. How is there no stop button/mechanism?!?
Yup - seeig this now. Two migrations running on a local device. Bounced the app - even removed the plugin and re-installed.
This functionality would really help us so much. I am currently migrating so many customers to the cloud and forced to use the site-import because the Atlassian Cloud Migration Assistant do fail in most of the time. If I use ACMA I need to wait until the end to start fixing the problems and re-start the migration. With the site-import it usually stops by itself when there is an issue. I guess the scheduler should clean up all the jobs at the start-up of the app. Like this we can just disable the app and re-enable it to stop the migration jobs.
The migration plan keep running, I have to reset Jira cloud and start the new migration plan, but this issue still occur.
I opened a ticket with support and they told me what I needed to do to. I needed to track down my sysadmin, as we needed database access as well as the ability to start/stop our Jira server instance.
It seems to be a problem with the 1.5.3 version of the migration tool - so stay on 1.5.2 (at least until the problem is fixed!)
I also have the same issue. Exporting users has been running for 12 hours. Please fix
My migration appears to be "in an infinite loop" on "Exporting Users". I assume this is happening because of an outage on the Atlassian servers. In situations like this, it's imperative that we be able to kill migrations — I could, for example, be migrating my projects without users instead of wasting time waiting around for the problem on the server to be resolved. I'm going to open a ticket with customer support and hopefully they can kill the migration.
Some customers may be experiencing issues with Account Management, Authentication Policies, Admin Insights and Domain Claims
Incident Report for Atlassian Access[Subscribe to Updates|https://access.status.atlassian.com/incidents/nnngwrbw3x87#subscribe-modal-nnngwrbw3x87]
Investigating
We are currently investigating the issue. At the moment we know of the service that is failing and are trying to find the root cause.
Posted 31 minutes ago. May 18, 2021 - 18:52 UTC
Even restart of the Jira server doesn't work. The Job keeps running
https://getsupport.atlassian.com/browse/MOVE-1747738