Upgrade guide

Owned by No Reply
Last updated: Oct 22, 2021 by Jonathan Muse

Looking for the documentation on the newest versions of Power Scripts for Jira 8 for Server/Data Center? Click here !

Content in development.

Once you upgrade to version 4.0.0, and data is migrated to this version, you will not be able to downgrade. That's why we recommend upgrading on a test instance first to check if everything works fine.

Possible "errors"

We're working to make the upgrade experience as smooth as possible. However, there are a few "errors" you may see in the logs that are actually normal. 


Unable to create a service config for service with the name <service_name>

Unable to create a service config for service with the name : asdf
com.atlassian.jira.service.OfBizServiceConfigStore$ClassNotFoundServiceException: Could not find class: com.keplerrominfo.jira.plugins.jjupin.services.SILService
        at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(OfBizServiceConfigStore.java:249)
        at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceContainer(OfBizServiceConfigStore.java:209)
        at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForId(OfBizServiceConfigStore.java:180)
        at com.atlassian.jira.service.DefaultServiceManager.removeService(DefaultServiceManager.java:480)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
....
Caused by: java.lang.ClassNotFoundException: Class 'com.keplerrominfo.jira.plugins.jjupin.services.SILService' not found.
        at com.atlassian.jira.plugin.DefaultComponentClassManager.constructEvenIfNotEnabled(DefaultComponentClassManager.java:160)
        at com.atlassian.jira.plugin.DefaultComponentClassManager.newInstance(DefaultComponentClassManager.java:72)
        at com.atlassian.jira.service.OfBizServiceConfigStore.loadServiceClass(OfBizServiceConfigStore.java:385)
        at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(OfBizServiceConfigStore.java:244)
        ... 170 more

Explanation

In version 4.0.0 we've moved our services to run with the Atlassian Scheduler library instead of the old services API. This error appears because at the end of the data migration, we attempt to delete the old services that are no longer needed. When removing a service, the services API attempts to instantiate it if it's not already available and since since the old implementation is no longer available, the instantiation will fail with the above error, but the service will be deleted as intended.

Actions needed

None