Project Configurator - A error raised when import a project configuration

Haishen July 10, 2018

I'm trying to import a project configuration to a JSD instance use Project Configurator, when I uncheck the ‘Apply changes?’, everything is fine, but when I check this option and do the real action, it report this error:

INFO  05:45:50,863 [Project IN] [Service Desk] Creating Request Type Windows Sever Services
ERROR 05:45:50,877 java.lang.NullPointerException
    at com.awnaba.projectconfigurator.loaders.handlers.RequestTypeHandler.createNewTargetFrom(RequestTypeHandler.java:211)
    at com.awnaba.projectconfigurator.loaders.handlers.RequestTypeHandler.createNewTargetFrom(RequestTypeHandler.java:1)
    at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler$3.createNewFrom(AbstractIntegratedHandler.java:210)
    at com.awnaba.projectconfigurator.loaders.core.AbstractSmartCreator.smartCreate(AbstractSmartCreator.java:13)
    at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.shallowCreate(AbstractIntegratedHandler.java:225)
    at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.createTarget(AbstractIntegratedHandler.java:171)
    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.core.AbstractIntegratedHandler.handleSubordinateCollections(AbstractIntegratedHandler.java:307)
    at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.handleSubordinatesAndProperties(AbstractIntegratedHandler.java:233)
    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:120)
    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.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)

1 answer

1 accepted

0 votes
Answer accepted
Kristian Walker _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 12, 2018

Hi Bai,

Thank you for your question.

I can confirm that this error indicates that the Windows Sever Services request type uses a custom request type icon which Project Configurator is able to set during an import.

In order to workaround this can you please try settimh all of the icons used by the request types in the IN project to use a default request type icon before taking a new export to import from. 

If this answer has solved your issue can you please accept it in order to mark this answer as correct for users who are searching for a similar issue.

Regards,

Kristian

Haishen July 12, 2018

Hi Kristian

Thanks for the quick response.

I tried to reset the request type icon before export and seems not work.

And I can't find any  relevant information of icons in XML, so how does the icon be set when import?

Kristian Walker _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 13, 2018

Hi Bai,

Thank you for your response.

I have spoken to my colleagues about this issue and we have noticed that there is an issue when exporting and importing request types in the 2.3.8-J7 version of project configurator.

Can you please try updating both the source and target instance to use version 2.3.7-J7 before ensuring that no custom request type icons are used.

You will then to need to take a new export with version 2.3.7-j7 and will need to import this using version 2.3.7-j7 in order to see if the issue is resolved.

Regards,

Kristian


Haishen July 13, 2018

Hi Kristian

It worked!! Thanks

I notice that in the file 2.3.7-J7 exported there is a section named "iconId" under "requestType" , but it disappear in 2.3.8-J7, is it an issue or you guys just remove this in 2.3.8?

Kristian Walker _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 13, 2018

Hi Bai,

We noticed this was an issue in 2.3.8-J7 and we are planning to fix this so that it will work again in the next version. 

Thanks

Kristian

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events