My votes: Azure DevOps Services and Server
Sort by:
Recent
Status:
Future consideration
Showing 86
17
VOTE
Include Area Path in VSTS Integration
I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
3
Future consideration
12
VOTE
Control how Estimates are converted and sent to TFS/VSTS
The default behaviour of how the TFS/VSTS integration sends time Estimates in minutes is very limiting.
I don't know any agile team that would be estimating Features or Requirements down to minutes, so it doesn't make sense for the integration to ...
1
Future consideration
3
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...
0
Future consideration
5
VOTE
Add ability to transfer requirements between features and features between master features (epics)
If you take the typical hierarchy VSTS, of Epics, Features and Product Backlog items, its is great that with Integrations 2.0 we can map these to Master Features (we call these Epics), Features and Requirements (we call this PBI's).
However we are...
0
Future consideration
55
VOTE
Configurable destination of imported features
As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
9
Future consideration
19
VOTE
