Azure DevOps Services and Server

What is the challenge? We did work in prior features to maintain integration links when records move across projects in ADO. Now, if a record moves across projects in ADO and workspaces in Aha! the record link breaks. What is the impact? D...

What is the challenge? Integration links can be lost for a variety of reasons. For organizations with a large number of records, it is not realistic to manually relink or reimport their backlog when this happens. What is the impact? Suppor...

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 ...

What is the challenge? Integrations have been setup using an integration template and they are associated to multiple workspaces. When a feature is created in workspace 1 and connected to an epic in workspace 2 an error is received when the fea...

What is the challenge? Syncing multiple values between ADO <>Aha! requires support for the Multivalue control extension to work. Syncing editable choice lists works, pre-defined lists only sync 1 value when 2 or more are selected. What...

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 integra...

What is the challenge? There is a tool to aid users in migrating from Jira server to Cloud, but it does not currently support ADO migrations. What is the impact? Users who need to migrate ADO have a manual process to relink records after moving to...

What is the challenge? When a parent or a child record is moved to another workspace in Aha! it will no longer update via integrations due to the child and parent existing in different workspaces in Aha! What is the impact? Integrations break when...

Who would benefit? Anyone who manages an Aha board that syncs with Azure DevOps (ADO) What impact would it make? It would reduce out-of-date information in Aha & on roadmaps from records that rely on the ADO integration for updates. Additional...

I understand you've created the dependency link in Aha! with Jira, it would be great to have this in ADO (Azure DevOps) too please