Skip to Main Content

Share your product feedback

ADD A NEW IDEA

My ideas: Azure DevOps Services and Server

Showing 108

Add warning text to Custom field Key field description that changing the key value will break integration

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...
Rob Boutmy over 1 year ago in Azure DevOps Services and Server 0 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 over 6 years ago in Azure DevOps Services and Server 1 Future consideration

Better presentation of text when integrating to an existing field in ADO

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...
Jake Hawkes over 1 year ago in Azure DevOps Services and Server 0 Future consideration

ability to integrate idea information into Azure DevOps

We use the ideas portal to solicit new enhancements from our users and then link those ideas to features in our products. The problem is only our product management and dev management use Aha. our development team uses Microsoft DevOps to track th...
Joe Granville over 5 years ago in Azure DevOps Services and Server 0 Future consideration

Allow link of a requirement to a release (sprint)

We have features that are mapped to a specific sprint, but within that feature, we have requirements (user stories) that could be mapped to two different sprints. The assumption with Aha! is that a feature would be completed in one sprint, which i...
Guest almost 2 years ago in Azure DevOps Services and Server 0 Future consideration

Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO

Given that AHA is all about releases and ADO is all about time lines, the concept of a Release in AHA is quite different than what exist in ADO - yet there is a Target Release field in ADO as well as in the Feature of AHA - please can this be expo...
Dirk K over 3 years ago in Azure DevOps Services and Server 1 Future consideration

Configure iterations based on phases in DevOps

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...
Carlo Bril over 3 years ago in Azure DevOps Services and Server 0 Future consideration

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

Properly transfer images in VSTS comments to Aha!

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

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 4 years ago in Azure DevOps Services and Server 3 Already exists