Auto-Import children option can import the hierarchy into wrong nodes in 16.1.3
search cancel

Auto-Import children option can import the hierarchy into wrong nodes in 16.1.3

book

Article ID: 277611

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

STEPS TO REPRODUCE
1. Create two custom investments: CustInv1 and CustInv2
2. Include them in Hierarchies
3. At the first custom investment create two instances: Cust1A and Cust1B
4. At the second custom investment create for instances: Cust2A, Cust2B, Cust2C, Cust2D
5. On the CustInv2 instances set the following parent relationship
   Cust2A parent is Cust1A
   Cust2B parent is Cust1A
   Cust2C parent is Cust1B
   Cust2D parent is Cust2C


6. Create a Hierarchy and import Cust1A and Cust1B
7. On the Hierarchy view right click on Cust1A and Auto-Import children
   Cust2A and Cust2B are imported as immediate children


   On the Hierarchy view right click on Cust1B and Auto-Import children
   Cust2C and Cust2D are imported. Cust2C as an immediate child and Cust2D as a child of CustC


8. On the Hierarchy view right click on Cust1A and Auto-Import children

Expected Results: No changes to be done to the hierarchy as no parent relationship has changed at the investment level 
Actual results: Cust1A loses its hierarchy and every child is imported to Cust1B 

Environment

Clarity 16.1.3

Resolution

This is fixed in 16.2.0