ConnectALL does not maintain Parent-Child structure in ALM for Business and Functional Requirements
search cancel

ConnectALL does not maintain Parent-Child structure in ALM for Business and Functional Requirements

book

Article ID: 433317

calendar_today

Updated On:

Products

ConnectAll On-Prem ConnectALL ConnectAll SaaS

Issue/Introduction

When integrating JIRA to ALM, the parent-child relationship between synced issue types is not always preserved.

For example,

  1. NewFeature (JIRA) --> Business Requirement (ALM) > Parent Automation
  2. NativeDev (JIRA) --> Functional Requirement (ALM) > Child Automation

If NativeDev issues are created as children under a New Feature in JIRA, users expect ALM to maintain this Parent-Child relationship between the respective Business and Functional Requirements.

However, this structure may fail to sync properly, resulting in subtasks being created outside of their designated parent folder.

Environment

ConnectALL 4.0

Cause

This issue is caused by incorrect configuration mapping for subtask automation.

Specifically, incorrect parent field mappings and having issue linking enabled can prevent the Translate Record ID function from correctly assigning the child records to their proper parent folders in ALM.

Resolution

To address this issue and properly maintain the parent-child hierarchy during synchronization, you must apply the correct configuration required for subtask automation. Apply the following steps to your automation configuration:

 

  1. For Child Automation, disable Issue Linking on the Entity Mapping tab.
  2. Remove the existing field mapping: Parent <> Parent Folder.
  3. Add the new field mapping: SubTask Parent ID <> Parent Folder.
  4. Click on the gear icon for the new field mapping (SubTask Parent ID <> Parent Folder) to enable the Translate Record ID configuration.
  5. Check the checkboxes next to Translate Record ID for both ALM and Jira.
  6. Under automation, select the parent automation which syncs Business Requirements.
  7. Save the changes and verify the sync.

 

Note: Any existing Functional Requirements that were created outside the parent folder will automatically be fixed and moved to the correct hierarchy once they receive an update.