RELATED IDEAS
Sending child records to one ADO project should not error out if parent record is integrated to a different Workspace and ADO project
What is the challenge? |
Users are now able to support linking work between multiple Aha! workspaces and multiple ADO projects with parent/child relationships spanning this; however one scenario is producing an error. When a parent record is integrated from one workspace or parent line to one ADO project and a user tries to send a linked child record from a different workspace to a different ADO project, the record fails to send. |
What is the impact? |
To work around this, users can unlink the parent record, send the record to ADO and then re-add the parent link, but this is a manual process. |
Describe your idea |
The record should integrate successfully without any manual workaround with the correct parent/child relationship displayed in both systems. |
© 2025 Aha! Labs Inc.•All rights reserved
This is a substantial problem at our organization because we have so many teams working across different ADO area paths. When the data is out of sync people lose faith in Aha! reports because they do not represent accurate up to date information. On top of that the administrative time to reconcile the issues is quite costly. Thank you for your consideration.