ConnectAll Jama Adapter - ID of paired application mapped to custom Jama field fails on creation syncback

Products

• ConnectALL
• ConnectAll On-Prem
• ConnectAll SaaS

Issue/Introduction

Jama Adapter - ID of paired application mapped to custom Jama field fails on creation syncback.

Steps to Reproduce: 

1. FOR EPICS
2. Map the Name and Description fields, and set a _CONSTANT for the Jama parent Set.
3. Map the Jira Key to a custom string field in Jama
4. Save the automation
5. Create a Story in Jama
6. After syncing the Story to Jira, observe how the syncback of the Jira Key fails with the below error message
   1. Error Message :  Record could not be updated due to the error {"meta":{"status":"Bad Request","timestamp":"2025-09-24T00:24:16.562+0000","message":"You cannot move this item to the root of the project"}}
7. This is the same message that is thrown if you try to make an update to Jama without the _CONSTANT -> Parent mapping. This means ConnectALL is ignoring the constant when syncing the Jira Key back to Jama at creation time.

Expected Results: 

• Success on creation syncback

Actual Results:

• Failure on creation syncback

Environment

3.9.1

Cause

DE176276 

Resolution

Fixed in future release.