Skip to Main Content
ADD A NEW IDEA

Azure DevOps Services and Server

Showing 88

Add the work item Id to the Import new records dialog

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
David Beaumier almost 4 years ago in Azure DevOps Services and Server 5 Future consideration

Ability to search for key words in Integration updates when importing new records

After the updated TFS integration which allows records to be imported directly from TFS into Aha. It would be ideal to be able to search the new record list for key words. Currently you can filter the list but this is not very user friendly and if...
Guest about 6 years ago in Azure DevOps Services and Server 0 Future consideration

Auto Renew Webhooks

Annoying maintenance task of updating expired webhooks that keep making systems out of sync and we end up using VSTS as the source of truth rather than Aha!
Guest over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Allow parent mapping of releases to initiatives

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.
Joe Granville over 4 years ago in Azure DevOps Services and Server 0 Future consideration

Allowing integration configuration to use queries to limit dataset integrated.

We have a shared devops environment that is managed by others and possibly not configured in the optimal way - especially when we try to integrate. Ideally, the same queries we use to "import" data (that we can modify) could persist to limit the d...
Guest over 2 years ago in Azure DevOps Services and Server 1 Future consideration

ADO Server Import to Aha Ideas

No description provided
Sara Olson over 2 years ago in Azure DevOps Services and Server 0 Future consideration

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...
Guillaume Metman almost 5 years ago in Azure DevOps Services and Server 0 Future consideration

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...
Dan Orth over 2 years ago in Azure DevOps Services and Server 0 Future consideration

Integration by status

I'm not sure how much demand there would be for this, but I've had a need a few times for it so I'm going to suggest it. I would like to be able to limit automatic integration of new requirements if they are in a certain state, such as New. If a f...
Tom Beck over 5 years ago in Azure DevOps Services and Server 0 Future consideration

Sending Sprint to VSTS with complex organization

I can't get my Sprint to land in the right area, it winds up under main as another project instead of sprint under a project when structure is Main>Project>Sprint.
Guest over 5 years ago in Azure DevOps Services and Server 0 Future consideration