Epics in Visual Studio Online (VSO)

Epics on top of feature were introduced with VSO a few weeks ago.

The VSO Connector should be able to reflect that somehow. Either by also working with epics in aha that encapsulate features or better the easy MVP way with a global setting for the VSO Connector to create features or epics in VSO from aha.io features. 

  • Fabian Henzler
  • Jun 17 2015
  • Shipped
Release time frame
  • Feb 26, 2018

    Admin Response

    We have launched enhanced VSTS and TFS integrations. These integrations will allow you to link Aha! records to epics in VSTS and TFS 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
  • Jim Payne commented
    October 13, 2015 17:27

    VSO has (currently) one level of Epics and multiple levels of features and Aha has multiple levels of intiatives, So synching to Aha may be different for every company. Epics definitely need to get into the act, but I think we need a way to control whether an initiative at a particular level creates an Epic or a Feature and - for sure - that the hierarchy of initiatives in Aha is reflected as links in VSO.

  • Joel Stoddard commented
    July 21, 2016 14:37

    It would be great to see this integration move forward. I understand Jim's point on flexibility, but it would also be nice to see some progress here.  I am currently replicating the structures manually and it is painful.

  • Guest commented
    December 19, 2016 19:05

    Any updates on this?