Migrations from Jira Software 7.9.2 to Jira Cloud

fsilvera April 12, 2023

Good afternoon,
I would like to know if there is a tool to migrate from Jira Software v7.9.2#79002 (onsite) to Jira Cloud.
I installed the "Jira Cloud Migration Assistant" plugin but it fails when trying to enable it
"Error enabling Jira Cloud Migration Assistant plugin (com.atlassian.jira.migration.jira-migration-plugin)"
Could you tell me if there is a way to enable it or migrate it.
Thank you

1 answer

1 accepted

0 votes
Answer accepted
Hana Kučerová
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 12, 2023

Hi @fsilvera ,

welcome to the Atlassian Community!

JCMA should be available for Jira v7.9.2. Have you tried to look into Jira logs, why it is not possible to enable it?

fsilvera April 12, 2023

Good afternoon Hana,

Thank you for the welcome and your answer. I copy and paste some of the logs I see into

/var/atlassian/application-data/jira/log/atlassian-jira.log

 

2023-04-12 17:03:00,922 http-nio-8080-exec-49 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1):
[com.atlassian.jira.migration.jira-migration-plugin], 267 seconds remaining
2023-04-12 17:03:01,600 ThreadPoolAsyncTaskExecutor::Thread 27 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.j.migration.version.AppOutdatedInfoProvider] Ap
p Outdated Service base uri : https://api.atlassian.com/migration/
2023-04-12 17:03:01,718 ThreadPoolAsyncTaskExecutor::Thread 27 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.j.migration.migrationservice.MigrationServiceCl
ient] migration service base url : https://api-private.atlassian.com/migration/
2023-04-12 17:03:01,724 ThreadPoolAsyncTaskExecutor::Thread 27 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.j.migration.mediaclient.MediaClient] media base
url: https://api.media.atlassian.com
2023-04-12 17:03:03,820 http-nio-8080-exec-49 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1):
[com.atlassian.jira.migration.jira-migration-plugin], 264 seconds remaining
2023-04-12 17:03:03,821 ThreadPoolAsyncTaskExecutor::Thread 27 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.j.migration.orchestratorclient.MigrationOrchest
ratorClient] orchestrator base url: https://api-private.atlassian.com/migration/orchestrator/api/plugin/
2023-04-12 17:03:04,350 ThreadPoolAsyncTaskExecutor::Thread 27 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.j.migration.usersmigrationservice.UsersMigratio
nServiceClient] users migration service base url : https://api-private.atlassian.com/migration/
2023-04-12 17:03:06,624 http-nio-8080-exec-49 INFO fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1):
[com.atlassian.jira.migration.jira-migration-plugin], 261 seconds remaining
2023-04-12 17:03:06,751 ThreadPoolAsyncTaskExecutor::Thread 27 ERROR fsilvera 1022x806933x1 1yl50rh 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [c.a.p.osgi.factory.OsgiPlugin] Unable to start the
plugin container for plugin 'com.atlassian.jira.migration.jira-migration-plugin'
java.lang.NoClassDefFoundError: com/atlassian/servicedesk/api/ServiceDesk
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
at java.lang.Class.getDeclaredMethods(Class.java:1975)
at org.springframework.util.ReflectionUtils.getDeclaredMethods(ReflectionUtils.java:609)
at org.springframework.util.ReflectionUtils.doWithMethods(ReflectionUtils.java:521)
at org.springframework.util.ReflectionUtils.doWithMethods(ReflectionUtils.java:507)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.determineCandidateConstructors(AutowiredAnnotationBeanPostProcessor.java:241)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.determineConstructorsFromBeanPostProcessors(AbstractAutowireCapableBeanFactory.java:1069)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1042)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:510)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: com.atlassian.servicedesk.api.ServiceDesk not found by com.atlassian.jira.migration.jira-migration-plugin [257]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1532)
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:75)
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1955)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 25 more
2023-04-12 17:03:06,759 Gemini Blueprint context shutdown thread2 WARN fsilvera 957x805094x1 1uqb26s 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migration-plugin-key [o.s.osgi.atlassian.NonValidatingOsgiBundleXmlAppl
icationContext] Exception thrown from LifecycleProcessor on context close
java.lang.IllegalStateException: LifecycleProcessor not initialized - call 'refresh' before invoking lifecycle methods via the context: NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.migration.jira-migration-plugi
n, config=osgibundle:/META-INF/spring/*.xml): startup date [Wed Apr 12 17:02:28 ART 2023]; root of context hierarchy

fsilvera April 12, 2023

.

fsilvera April 13, 2023

Good morning Hana,
How are you? These are the errors I found in the logs. thanks for your help

 

2023-04-13 10:11:38,567 ThreadPoolAsyncTaskExecutor::Thread 29 ERROR fsilvera 611x810014x1 1d5strq 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migr
ation-plugin-key [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.jira.migration.jira-migration-plugin'
java.lang.NoClassDefFoundError: com/atlassian/servicedesk/api/ServiceDesk

2023-04-13 10:11:48,574 ThreadPoolAsyncTaskExecutor::Thread 29 ERROR fsilvera 611x810014x1 1d5strq 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migr
ation-plugin-key [o.e.g.b.e.i.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jir
a.migration.jira-migration-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the
thread still hangs

2023-04-13 10:11:48,581 ThreadPoolAsyncTaskExecutor::Thread 29 ERROR fsilvera 611x810014x1 1d5strq 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migr
ation-plugin-key [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassia
n.jira.migration.jira-migration-plugin, config=osgibundle:/META-INF/spring/*.xml))
java.lang.NoClassDefFoundError: com/atlassian/servicedesk/api/ServiceDesk

2023-04-13 10:11:48,582 ThreadPoolAsyncTaskExecutor::Thread 29 ERROR fsilvera 611x810014x1 1d5strq 192.168.0.11 /rest/plugins/1.0/com.atlassian.jira.migration.jira-migr
ation-plugin-key [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.jira.migration.ji
ra-migration-plugin], unsatisfied dependencies: none
java.lang.NoClassDefFoundError: com/atlassian/servicedesk/api/ServiceDesk

Hana Kučerová
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 13, 2023

Hi @fsilvera ,

thank you.

It is strange that the errors are connected to Service Desk - was Jira Service Desk / Management product formerly installed in your instance?

Anyway, I think it will be the best to create migration support issue directly to Atlassian to help you with this.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events