JAMA-JIRA entity relationship sync fails with "Relationship violates rules" - ConnectAll
search cancel

JAMA-JIRA entity relationship sync fails with "Relationship violates rules" - ConnectAll

book

Article ID: 440027

calendar_today

Updated On:

Products

ConnectAll On-Prem ConnectALL ConnectAll SaaS

Issue/Introduction

When syncing parent-child relationships between Jama and Jira using ConnectAll, child records may sync without their parent relationship. This occurs when Jama relationship rules block the connection.

 

Steps to Reproduce: 

  • Login to Jama Application.
  • Click on Admin-->Relationship tab.
  • Add a new relationship between any Upstream and Downstream entities.
  • Create a parent an automation in connectAll between Jama>Jira.
  • Do required basic field mapping.
  • Sync records for Parent Automation.
  • Create a child automation in connectAll between Jira>Jama.
  • Create a recored in Jira, link to ticket created via parent automation.
  • Sync record .

Expected Results: 

  • Record created via child automation in Jira should be synched in Jama along with relationship

 

Actual Results:

  • Record getting created via child automation synched to Jama without showing any relationship in Jama  with parent record. Below exception seen in automation logs.

Exception in Creating the UpStream Issue Links
java.lang.Exception: Record could not be created due to the error {"meta":{"status":"Bad Request","timestamp":"2026-04-27T11:23:05.731+0000","message":"Relationship violates rules configured for the project: from item ID: #1234, to item ID: #4321"}}
at com.go2group.connectall.RESTBasicAuthConnector.createRecord(RESTBasicAuthConnector.java:334) ~[Connectors-4.0.1.jar!/:4.0.1]

 

 

 

 

Environment

4.x

Cause

Jama's internal relationship ruleset restricts connections between specific Upstream and Downstream item types, which prevents the ConnectAll API from establishing the link.

Resolution

  • Login to Jama Application.
  • Click on Admin-->Relationship tab.
  • Select the checkbox to bypass configured rulesets i.e. "Allow any item type not mentioned in this rule set to be related to any item type including those in the rule set"