Support parent/child relationships for records integrated on different tools or instances

What is the challenge?

Scenario 1:

• A parent initiative in Aha! is integrated with Jira instance 1

• A child epic in Aha! is integrated with Jira instance 2

Scenario 2:

• A parent initiative in Aha! is integrated with Rally

• A child epic in Aha! is integrated with Jira

What is the impact?

Updating the epic in either scenario will cause a duplicate initiative to be created:

• Scenario 1: a duplicate initiative will be created in Jira instance 2

• Scenario 2: a duplicate initiative will be created in Jira

Describe your idea

New check when sending updates of child records over the integration: Check if the parent is integrated with a different tool or a different instance:

• If yes, do not include the parent record in the payload when sending the child to it's integrated system.

• If no, send the parent to the same integrated tool/instance (current behaviour)

This would need to apply to all parent/child relationships.