Allow scheduled update of all linked records for DevOps
As the service hooks from DevOps to Aha are seldomly failing, it often results in having some records not in sync in Aha. This can be solved by running an update of all the linked records from the Aha integration page, but this requires to be manu...
I'd like to be able to easily see if our engineers remembered to add the PR to each completed feature. Currently it doesn't look like this integration field is available to include in reports.
We often create features in Aha and sync them into DevOps for the Dev Team. Our dev team then creates the user stories and syncs those back to Aha. They use a small grid in their user story template in DevOps. When it syncs back, that grid is oddl...
Better handling of when Features are removed from a Sprint
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...
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...
Custom Record Type, Made Up Entirely Of Custom Fields
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...
In ADO we use assign our epics as children of themes. In AHA we map themes to initiatives and epics to releases but in the integration configuration we cannot set the parent mapping.
Azure DevOps or JIRA integration : allow some way to automatically select which integration to use when more than one exists in a product
We usually map 1 Aha Product to 1 AzDo project, in which case everything is fine (except that everything ends up in the same Area Path). We can also easily map N Aha Products to 1 AzDo project, mapping each Product to an AzDo area path. But we cur...