RELATED IDEAS
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!
© 2024 Aha! Labs Inc.•All rights reserved
The Area Path is defined in the integration I believe as 1-1 with the project. Rather than mapping, could one not use the integration as a template and create an integration for each Area Path? Then you could select which Team to send work to by selecting the associated integration. I placed a similar request but for being able to identify the default iteration path used for the team backlog as defined in the Team Settings for the project; for team who are not on the same cadence.
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.
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.