Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Azure DevOps Services and Server

Showing 118

Allow integration with custom work item types

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...
Guest about 5 years ago in Azure DevOps Services and Server 3 Already exists

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 over 5 years ago in Azure DevOps Services and Server 5 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 about 6 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 over 6 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 about 7 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 about 7 years ago in Azure DevOps Services and Server 0 Future consideration

Don't fail TFS Integration when attached file is too large

When a file has been uploaded to aha that is larger than the maximum file size,then integrate without the file in TFS, adding a note indicating this. This will allow the team to collborate on the TFS items without having to delete the file.
Guest over 7 years ago in Azure DevOps Services and Server 0 Future consideration

VSTS updating Aha! features base user stories

Leadership and executives are using Aha! more and more. Having the ability to represent the percentage completed of features in a given release is very important when reporting to large audience. I like to ability to show the percentage of the Fe...
Guest over 7 years ago in Azure DevOps Services and Server 0 Already exists

Would it be possible to not need a paid AHA account to process VSTS updates?

At the moment we have set up the VSTS integration with a paid AHA account as required. This means that all updates come in from that product manager. In the history threads, and the notification emails we get a combination of VSTS updates, and the...
Guest about 9 years ago in Azure DevOps Services and Server 1 Unlikely to implement

Support Modern OAuth Authentication Instead of PAT for Aha! Roadmaps Azure DevOps Integrations

We are currently using Aha! Roadmaps and asking for consideration of implementing OAuth authentication when setting up the integration to Azure DevOps Services. With Microsoft making the push towards strengthening their customers security posture,...
Guest 4 days ago in Azure DevOps Services and Server 0 Future consideration