Azure DevOps Services and Server

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...

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

Converting a requirement to a feature will cause the record to lose some custom field information because features may not have the same custom fields. We can choose whether or not to proceed. There's no mention of integration to an external syste...

In TFS one can create personal access token in order to integrate with 3rd party apps. Would be great if Aha! would accept that token instead of user name and password.

As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...

In the new integrations 2.0 I can't find a way to set the Iteration Path. While I very much appreciate the new functionality in 2.0 that was a very convenient mapping in order to create work items in a specific Iteration Path.

To be able to easily create bugs from within Aha and use the TFS integration to pull across all relevant info from the description field into reproduction steps. After a long investigation by Aha they found that this link was not created as part o...

If we have pushed the item and edit (add story or attachments) it doesnt update VSTS, This means requirement could be missed.

It would be useful if Aha allowed for mapping of Master Features the same way it allows Features to be mapped.