Epic / Initiative parent link does not sync between Jira and Rally - ConnectALL
search cancel

Epic / Initiative parent link does not sync between Jira and Rally - ConnectALL

book

Article ID: 444888

calendar_today

Updated On:

Products

ConnectAll On-Prem

Issue/Introduction

When synchronizing artifacts between Jira and Rally, the parent-child relationship between newly created Epics and Initiatives fails to establish in Rally. While field updates to individual artifacts sync correctly, the hierarchical link remains missing in Rally until a manual intervention is performed (forcing a sync).".

The field is set to translate recordID and Fail on Rally side and Clear on Jira side.

Symptoms:

  • Newly created Epic/Initiative pairs do not show the parent relationship in Rally.
  • Updates to fields like labels or descriptions sync successfully, but the Parent link is not established.
  • No failure or error is recorded in the logs.

Steps to Reproduce: 

  1. Created Initiative & Epic 
     
  2. Rally Created URLs & ID without parent relationship on Rally Epic
     
  3. I updated a label on Jira Epic and that got synced to Rally Epic and the parent info still not got synced
     
  4. Again I updated the Label on Initiative and Epic both labels info got synced to rally. But still Rally Epic the parent not updated
     
  5. I did a manual sync with Epickey - issueID, now the Parent info got synced. Here I did a force sync without any field update that got synced the parent info

Expected Results: 

  • The artifacts are linked successfully.

Actual Results:

  • The epic/initiative pair this relationship isn't getting created in Rally

Workaround: 

  • Run a force sync without any field updates

Environment

ConnectALL On-Prem 4.2.0 and 4.0.6

Cause

DE205190: Epic/Initiative Parent link not linked on creation or after updates

This issue occurs when the timing of the synchronization cycle creates the child artifact before the parent artifact is fully indexed or available for linking in the destination system. The sync does not automatically re-attempt the link if it was missed during the initial creation cycle.

Resolution

This issue is currently under investigation by engineering (DE205190). It is targeted to be fixed in a future release.