Parent not synced by the Clarity-Rally Integration when set to both

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Rally Integration does not sync the Parent field when is set to run in both directions.

Steps to Reproduce:

1. Create Integration with Rally details in Clarity->Classic UI->Administration->Integrations
2. Create Integration Mapping in Clarity MUX->Administration->Integrations-> Add new Integration Mapping using Integration which is created at step 1.
3. Run "Import Integration Mappings" Job
4. Add the Object Mappings for below Rally Items
   Initiative - integration is set to run in one direction only -  from Clarity to Rally.
   Capability - integration is set to run in one direction only -  from Clarity to Rally.
   Feature - Integration is set to run in BOTH directions.
   Note: Add the Parent field mapping with direction BOTH (it allow only on "Update" as sync option)
5. Login to Rally UI.
6. Open the portfolio item feature - (Example : F1147 & F1146).
   Note: Make sure the Parent of this feature is Capability already synced, if not select the Integration Mapping field = "Clarity - Rally" and save for Capability
7. Now Set integration mapping field = "Clarity - Rally" and save.
8. Open Classic UI in new tab
9. Click on "home" --> select "Reports & Jobs" --> Click on JOBS.
10. Search for Job Type =Sync and enter.
11. Click on "Synchronize Mapped Information"
12. Here set the integration mapping = "Clarity - Rally" & set parameters "When = immediately"
13. Hit Submit.
14. Based on the step 6 and step 7, The Capability and Features are created in Clarity 
15. Now to populate the Parent field in Clarity instances, "Parent" field can be updated only on "Update" and so run the sync mapped information job once again expecting that it would bring "Parent" field in Clarity be updated in Clarity.

Expected Result: After second run of the "Synchronize Mapped Information" Job, the  "Parent" field in Clarity be updated.

Actual Result: After second run  of the "Synchronize Mapped Information" Job, the Rally Feature's Parent field updated as empty.

Environment

Release : 16.1.1

Cause

DE70279

Resolution

This issue has been fixed in Clarity 16.1.2 patch #1 and 16.1.3.

Additional Information

• In case of bi-directional ('BOTH'), it's recommended to have the user profiles in Clarity and Rally match the time zones, especially if Clarity and Rally are hosted in different time zones.
• As part of the integrations, when the date is synced, post syncing the data between the systems based on the mapped direction, the integration job updates the Last Sync Message and Last Sync Status fields on the Clarity instance, so, in this case, the Clarity instance will have the lastUpdatedDate later than the Rally instance's lastUpdatedDate, even the instance is created from Rally to Clarity.
• In this case, if the user runs the Sync Job a second time to update the parent field (or any of the OOTB lookup fields) without any update on the Rally instance, then the Sync Job will treat the Clarity instance as the updated one as opposed to the Rally instance, and this will try to override the parent field on Rally instance (it will take the direction as Clarity to Rally for the 'BOTH' as the Clarity instance is considered the updated one).