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.
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.
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.
Just add another layer of mapping to the existing config pane. Not everyone thinks Initiatives = Epics, but just make it configurable.
Any updates on this?
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.