Jira Cloud StatusCategory Mapping NullPointerException in ConnectALL

Products

• ConnectAll On-Prem
• ConnectALL
• ConnectAll SaaS

Issue/Introduction

When synchronizing data between Jira Cloud and Rally, the automation fails during the fetch process if the StatusCategory field is mapped. Users may observe that the synchronization works correctly in Jira Datacenter but triggers a java.lang.NullPointerException immediately after migrating to or setting up a new integration with Jira Cloud. This error prevents the synchback fields like "Rally Link" URL from being returned to the Jira record.

The following error may be seen in logs

ERROR YYYY-MM-dd hh:mm:ss,SSS -nnnnnnnnn | appLinkName | pollId | recordId | {groupName}][thread #nn] com.go2group.connectall.model.transformer.jira.rest.JiraRestConnectionManager: Error while fetching the record recordId due to java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "statusCategoryObject" is null

Environment

 

• Product: ConnectALL On-Premise

• Version: 4.0.0.0

• Integrated Systems: Jira Cloud, Rally

• Affected Entities: Story / User Story

 

Cause

The issue is caused by a failure in the JiraRestModelConverter when processing the StatusCategory object from the Jira Cloud REST API response. Specifically, the application attempts to invoke a method on a statusCategoryObject that returns as null, leading to a pointer exception during the record fetch phase.

Resolution

To work around this issue, the field mapping must be adjusted to use a compatible status field that Jira Cloud provides consistently.

1. Log in to the ConnectALL interface.

2. Navigate to the specific Automation (AppLink) between Jira Cloud and Rally.

3. Go to the Field Mapping tab.

4. Locate the mapping for Status Category (Jira side) mapped to Schedule State (Rally side).

5. Remove the Status Category mapping.

6. Add a new mapping using the standard Status field from Jira to the Rally Schedule State field.

7. Update the Value Mappings for the new Status field to ensure the states align correctly (e.g., To Do, In Progress, Done).

8. Save the automation and run a manual sync to verify the fix.

 

 

This defect is officially addressed in ConnectALL version 4.1.1.

Additional Information

 

The error may also present a secondary exception in the InlineAttachmentTransformer if the record cannot be initialized due to the primary fetch failure.