When integrating JIRA to ALM, the parent-child relationship between synced issue types is not always preserved.
For example,
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.
ConnectALL 4.0
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.
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:
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.