Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to have this sync with Aha!

  • Guest
  • Jun 27 2018
  • Future consideration
Release time frame
  • Attach files
  • Guest commented
    September 14, 2018 20:24

    I agree this would be so helpful as the backlog splits of in to more refined teams!  At the moment, when it gets close to development I will actually "lose" the stories/updates that get split into area path teams, and then I picked them up again when they get shipped and back to the main backlog. 

  • Garry Finch commented
    16 Aug 10:08

    This is also something I am keen on seeing. Having multiple (and growing) dev pods working in their own areas within Azure Devops, we need to be able to manage the sync between Aha and each pod area.