Azure DevOps Services and Server
Sort by:
Trending
Status:
Future consideration
Showing 107
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
1
VOTE
Iteration Path Integration with Aha & ADO
Though we have Iteration path integration between Aha and ADO. This is currently limited to show dynamic values for the integrations. Also the Iteration Path is based on the Area Path, the values of Iteration path cannot be filtered / shown releva...
1
Already exists
2
VOTE
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...
3
Already exists
3
VOTE
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...
0
Future consideration
3
VOTE
1
VOTE
Links to Azure DevOps items should be dynamically created based on integration settings
We underwent a branding change and had to update our Azure subdomain and after updating all our workspace integrations in Aha!, the hyperlinks (Azure DevOps Services url) were still pointing to the old subdomain and there is no way to refresh them...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved