Add a new idea Subscribe
Status Shipped
Categories Azure DevOps Services and Server
Created by Keith Burgess
Created on Apr 6, 2016

RELATED IDEAS

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-1457 Sync Initiatives with TFS.

Map Aha! initiatives to epics in TFS Merged

As currently implemented, we have to manually map the features we send to TFS to the corresponding epics.  The duplication of effort risks missing features or introducing errors, between the two platforms.  Putting timeline as quarter because we're just getting started with Aha.  In that time frame our new PM team will be getting up to speed and the need to stay organized will be critical.

  • Guest
    Reply
    |     Sep 8, 2017

    In my company, we can't even use Aha unfortunately till the mapping of Aha to VSTS is enhanced. Definitely need to be able to send stuff as Epics. Agree configurable is even better but would have simple initiatives to Epics as phase 1.

  • Jonathan Hansen-Granger
    Reply
    |     May 18, 2017

    Agree with Max Cascone's comment - would like the ability to configure/map epics from TFS to the desired object in Aha!. I personally would like to map Aha! Releases to TFS Epics.

  • Max Cascone
    Reply
    |     Feb 14, 2017

    Just add another layer of mapping to the existing config pane. Not everyone thinks Initiatives = Epics, but just make it configurable.

  • Guest
    Reply
    |     Dec 19, 2016

    Any updates on this?

  • Mat Wood
    Reply
    |     Jul 27, 2016

    I agree with this although support is required for different mappings of Aha elements to TFS epics as I'm not sure Initiative to Epic is a perfect depending how you work.