Allow full mapping of Master Features to VSTS
It would be useful if Aha allowed for mapping of Master Features the same way it allows Features to be mapped.
-
ADMIN RESPONSEFeb 26, 2018
We have launched enhanced VSTS and TFS integrations. These integrations will allow you to map Aha! master features along with several other new capabilities including the ability to:
- Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
- Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from VSTS/TFS)
- Automatically send outgoing changes from Aha! or choose to review and approve them
- Import records directly from VSTS and TFS to make getting started in Aha! easy
Check out the blog post for more details.
3
MERGED
3
MERGED
Sync Master Feature to Work item type in Visual Studio
It would be perfect if we have another level other than Features and Requirements in the Visual Studio integration.
So, in the integration we need to have Master Feature as well to be mapped to whatever work item type we choose on VS like Epics fo...
0
Shipped
© 2025 Aha! Labs Inc.•All rights reserved
Will we get an option regarding how we sync it with VSTS. My vote would be to match a Master Feature in Aha with an Epic in VSTS, but different companies follow difference processes in VSTS.
Any update with regards to how likely it is that this will be implementer ? It would make VSTS integration much more convenient.
Agree needed to be able to sync to areas or Features in Vs
This is a 'must have' feature for us as we use VSTS extensively. The more manual work to keep Aha and VSTS in sync the less likely we are to use Aha (path of least resistance.)