RELATED IDEAS
Support movement of linked records across ADO projects
What is the challenge? |
Moving records within Aha! will no longer break integration links to ADO, however if records are moved within ADO the integrations links may break. In order for this to work, integrations need to be connected to the same template and the field mappings have to be based on the template. |
|---|---|
What is the impact? |
Data is out of sync and becomes restrictive, there is no way to see what records lost a record link and there is no way to re-link at scale. |
Describe your idea |
Allow movement across projects within ADO and maintain the integration link. |
-
ADMIN RESPONSEFeb 4, 2026
We’ve improved how Aha! handles Azure DevOps work items that move between projects.
When an integrated ADO work item is moved to a different project, the Aha! integration now continues to work as expected. The link between records stays intact, and two-way sync continues using the new project as the active integration target.
Note: This functionality supports an advanced integration use case and is enabled on a per-account basis. If you would like this enabled for your account, please contact us at support@aha.io and we’ll be happy to help.
-
-
-
-
-
-
-
- +1
© 2025 Aha! Labs Inc.•All rights reserved