Import Aha Features as VSO Backlog Items

The way Aha is explained and shown in the support files and sacreenshots, the aha 'features' should be backlog items in TFS under the SCRUM template, not VSO Features. Until we hit this, Aha was wonderful. 

  • Guest
  • Apr 10 2015
  • Shipped
Release time frame
  • Oct 7, 2015

    Admin Response

    With the Visual Studio Online and Team Foundation Server integrations it is now possible to map features and requirements to any workitem item.

  • Attach files
  • Nathan Stephens commented
    May 13, 2015 14:10

    I agree!!! We use TFS to communicate with the dev group and give them their details but making everything into a Feature breaks our TFS deployment.  It would be great to have the choice to make a feature or backlog item or bug conditionial on the aha item

  • Jim Payne commented
    October 13, 2015 17:32

    I'm cool with Features mapping to Features and Feature/Requirements mapping to PBIs. Now we need Initiatives mapping to Epics and - OH MY - what will Aha Releases map to??