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.


  • John Karabaic
  • Apr 18 2017
  • Shipped
Release time frame
  • Feb 26, 2018

    Admin Response

    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.
  • Attach files
  • Guest commented
    May 16, 2017 14:49

    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.)

  • Ben Weeks commented
    October 12, 2017 20:00

    Agree needed to be able to sync to areas or Features in Vs

  • Frode Jensen commented
    December 21, 2017 10:37

    Any update with regards to how likely it is that this will be implementer ? It would make VSTS integration much more convenient.

  • Howard Behr commented
    December 27, 2017 03:11

    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.