Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 92
3
VOTE
Add ability to sync custom table one to many field with AZURE DevOps Fields
I would like to be able to sync a one to many custom field, that links ties to a custom table, we have added to our requirements (PBIs), with the iteration path from DevOps. This does not appear to be possible. The reason for this is that we have ...
0
Future consideration
1
VOTE
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...
0
Future consideration
2
VOTE
Fix sync of grid style between Aha and DevOps
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...
0
Future consideration
1
VOTE
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...
0
Future consideration
4
VOTE
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...
1
Future consideration
1
VOTE
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...
0
Future consideration
3
VOTE
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...
0
Future consideration
2
VOTE
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...
1
Future consideration
2
VOTE
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...
0
Future consideration
2
VOTE
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...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved