Azure DevOps Services and Server

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

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

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

Current VSO/TFS integration only allow to submit a feature/requirement from Aha! to TFS/VSOAn option to link a feature/requirement with an existing TFS/VSO work item would be helpful

We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps. Our estimation process is basically as follows: * Product Manager creates Feature in Aha * Product Manager send RFC...

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...

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