Importing a complete export from another instance (both at 7.3.3) stops the error: " Cannot get property 'name' on null object". It's not clear to me which object or property is causing the problem.
Can anyone point me in the right direction?
INFO 15:51:27,366 [Project VYTSUP] [Service Desk] Modifying default Event User to: admin
ERROR 15:51:27,368 java.lang.NullPointerException: Cannot get property 'name' on null object
at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60)
at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:190)
at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:46)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:299)
at com.awnaba.projectconfigurator.groovytools.servicedesk.EmailChannelGroovyTools$EmailChannelImpl.toString(EmailChannelGroovyTools.groovy:43)
at java.lang.String.valueOf(String.java:2994)
at java.lang.StringBuilder.append(StringBuilder.java:131)
at com.awnaba.projectconfigurator.loaders.handlers.ServiceDeskHandler$2.propertySetLogMessage(ServiceDeskHandler.java:111)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler$4.logMessageContent(AbstractIntegratedHandler.java:284)
at com.awnaba.projectconfigurator.loaders.core.AbstractLogger.log(AbstractLogger.java:23)
at com.awnaba.projectconfigurator.loaders.core.AbstractSmartPropertySetter.smartSet(AbstractSmartPropertySetter.java:13)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.processOnepropertyHelper(AbstractIntegratedHandler.java:300)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.processPropertyActionList(AbstractIntegratedHandler.java:261)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.handleSubordinatesAndProperties(AbstractIntegratedHandler.java:234)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler$1.doAndReturn(AbstractIntegratedHandler.java:175)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler$1.doAndReturn(AbstractIntegratedHandler.java:1)
at com.awnaba.projectconfigurator.utils.SmartErrorReporter.wrapSafely(SmartErrorReporter.java:99)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.createTarget(AbstractIntegratedHandler.java:172)
at com.awnaba.projectconfigurator.loaders.core.AbstractTargetHandler.handleTarget(AbstractTargetHandler.java:102)
at com.awnaba.projectconfigurator.loaders.core.CollectionMatcher.match(CollectionMatcher.java:27)
at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.handleOneTypeOfSubordinates(AbstractIntegratedHandler.java:322)
at com.awnaba.projectconfigurator.loaders.handlers.JiraProjectHandler.postProcess(JiraProjectHandler.java:777)
at com.awnaba.projectconfigurator.loaders.handlers.JiraProjectHandler$15.doAndReturn(JiraProjectHandler.java:741)
at com.awnaba.projectconfigurator.loaders.handlers.JiraProjectHandler$15.doAndReturn(JiraProjectHandler.java:1)
at com.awnaba.projectconfigurator.utils.SmartErrorReporter.wrapSafely(SmartErrorReporter.java:99)
at com.awnaba.projectconfigurator.loaders.handlers.JiraProjectHandler.finishHandling(JiraProjectHandler.java:737)
at com.awnaba.projectconfigurator.loaders.handlers.ProjectConfigLoader.loadOperations(ProjectConfigLoader.java:224)
at com.awnaba.projectconfigurator.loaders.handlers.ProjectConfigLoader.doLoad(ProjectConfigLoader.java:127)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectConfigImporterImpl.doImport(ProjectConfigImporterImpl.java:166)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectConfigImporterImpl.access$0(ProjectConfigImporterImpl.java:149)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectConfigImporterImpl$ConfigImporterTask.call(ProjectConfigImporterImpl.java:145)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectConfigImporterImpl$ConfigImporterTask.call(ProjectConfigImporterImpl.java:1)
at com.awnaba.projectconfigurator.operationsapi.impl.ImportJobRunner.runJob(ImportJobRunner.java:122)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectConfigImporterImpl.runImportConfigJob(ProjectConfigImporterImpl.java:121)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectConfigImporterImpl.importConfigurationSynchronously(ProjectConfigImporterImpl.java:97)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectCompleteImporterImpl.executeNextPhase(ProjectCompleteImporterImpl.java:247)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectCompleteImporterImpl.doCompleteImport(ProjectCompleteImporterImpl.java:195)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectCompleteImporterImpl.access$0(ProjectCompleteImporterImpl.java:188)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectCompleteImporterImpl$CompleteImporterTask.call(ProjectCompleteImporterImpl.java:145)
at com.awnaba.projectconfigurator.operationsapi.impl.ProjectCompleteImporterImpl$CompleteImporterTask.call(ProjectCompleteImporterImpl.java:1)
at com.awnaba.projectconfigurator.longrunningtasks.TaskHelperImpl$WrappingTask.call(TaskHelperImpl.java:67)
at com.awnaba.projectconfigurator.longrunningtasks.TaskHelperImpl$WrappingTask.call(TaskHelperImpl.java:1)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:458)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:426)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:216)
at java.lang.Thread.run(Thread.java:745)
Hi Michael,
Thank you for your question.
I have reviewed the stack trace provided and can confirm that it indicates that it is failing to set the default user for the automation rules inside of the VYTSUP project.
In order to work around this errror you should check what the default event user is in the project in the source instance and ensure that it is set to be the same user inside of the target instance as well as ensure that all automation rules are set to run as the default event user in the source instance before taking a new export to import from.
Also can you please try ensuring that you are using the latest version of Project Confihurator which is version 2.3.9-j7 as we have made some improvements around this error in recent versions.
If this response has resolved your issue can you please mark it as accepted so that other users can see it is correct when searching for similar answers.
Regards,
Kristian
Hi Kristian - I'm already at the latest version of the add-on.
I created the same default event user in the target instance and made sure it has JSD application access. There are no other JSD projects in the target instance because JSD is newly installed in order to accept the migrated JSD projects.
Despite all this, the same error occurs.
Are there any other actions I should take or settings I'm missing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
Can you please validate that the event user is valid in the source instance and if it is not can you please update this in the source instance before taking a new export to import from.
If you are still having issues can you please provide us with the atlassian-jira.log file and the import traces which are displayed on screen inside of text files in a ticket through the Project Configurator support portal so that we can review these to see if they provide further details on what the cause of the error is.
Regards,
Kristian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Kristian - Yes I've confirmed the user. I'll pick this conversation up on the support portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.