Azure DevOps Services and Server

In our Aha / Azure DevOps integration we are mapping sprints back to Aha using a custom field, similar to this article: https://www.aha.io/support/roadmaps/integrations/azure-devops/sync-sprints-between-aha-and-azure-devops The issue seems to be t...

Currently, if a user adds a comment to a User Story or Bug discussion in VSTS and embeds an image in the comment, the image doesn't come through with the comment that shows up in Aha!. This makes it difficult for the reader in Aha! to follow the d...

each requirement should have an acceptance requirement section that can sync to a user story acceptance criteria in TFS

We're using multiple layers of iterations within Azure DevOps. So a Release consists of multiple sprints. I would like to be able to map not only releases to iterations, but also phases to iterations. That way I can use Aha! as a single point of e...

We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...

Sometime companies use customized templates with custom work item types. Currently the ADO integration only supports integration with the standard types like "initiatives", "features", "Requirements". Our template supports a custom type called "PI...

We found that changing the key-field string of a custom field will break existing integrations with ADO where the custom field is synced to an ADO field. There is no warning or anything. This is a big risk to us and to the trust that integration r...

Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...

It would be useful to show the work item Id in the list of records available to import as it's easier to search for a specific identifier than a name

Sometimes, the feature in ADO already exists, and I want to link it to a feature in Aha. When I do this, I'm presented with an un-readable HTML output of the description fields, making is pretty much impossible to actually see the differences. See...