NullPointerException in logs when ConnectALL tries to orphan items from Jira

Products

• ConnectAll On-Prem
• ConnectALL
• ConnectAll SaaS

Issue/Introduction

When an issue is removed from Jira and ConnectALL attempts to apply the orphan strategy, nothing appears to happen.  Related artifacts does not show any successes or failures.

Further inspection in logs may indicate an error as follows:

ERROR YYYY-MM-dd hh:mm:ss,zzz [-nodeIdentifier | logPrefix | scheduleId | runStatusId | {groupName}][(orphan-flows) thread ## - JmsConsumer[findOrphanQ]] com.go2group.connectall.model.transformer.jira.rest.JiraRestConnectionManager: Exception in connection manager 
java.lang.NullPointerException: null
at java.base/java.util.Objects.requireNonNull(Objects.java:233) ~[?:?]
at com.go2group.connectall.model.transformer.jira.rest.json.SortSprintByCompletedDate.isOpenState(SortSprintByCompletedDate.java:37) ~[Connectors-4.0.1.jar!/:4.0.1]
at com.go2group.connectall.model.transformer.jira.rest.json.SortSprintByCompletedDate.compare(SortSprintByCompletedDate.java:19) ~[Connectors-4.0.1.jar!/:4.0.1]
at com.go2group.connectall.model.transformer.jira.rest.json.SortSprintByCompletedDate.compare(SortSprintByCompletedDate.java:9) ~[Connectors-4.0.1.jar!/:4.0.1]

 

 

Cause

DE182134

Resolution

Workaround

To prevent parsing issues, you should avoid using the following characters in sprint goals and sprint names until we have the issue fixed:

[  {  ,  =  ]  }

 

Resolution

This will be fixed in a future version of ConnectALL