Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-1743 Set the TFS Iteration and Area path per feature or requirement.

TFS integration - when creating a feature be able to set the tfs area. Merged

TFS integration  - when creating a feature be able to set the tfs area.  Currently you can only map one tfs area to a single feature. 

  • Guest
  • Apr 6 2017
  • Already exists
Release time frame
  • Apr 14, 2017

    Admin Response

    This is already possible. Each integration maps to a single TFS area and you can have multiple integrations per product. Create an integration for each TFS area you need to map to and then rename the integration (by clicking the name at the top of the integration configuration page) and add the area name into the name of the integration. Then when sending a feature to TFS you will see each of the integrations listed in the Actions menu, allowing you to pick which area to send the feature to.

    You can also send features to particular areas in bulk using bulk edit in the Features -> List view.

  • Tom Gimpel commented
    17 Nov, 2017 04:01pm

    Dupe of  APP-I-1743  - please combine so the votes total. Current workaround is not practical. 

  • Tom Gimpel commented
    17 Nov, 2017 04:00pm

    We have over 140 areas paths - this isn't practical. (it's also a duplicate item on here). Please combine it with the other so that the votes total. 

  • Karl Laird commented
    27 Sep, 2017 05:25am

    The proposed workflow is pretty clunky; especially in terms of trying to ensure the 'right' integration is chosen after the Feature has been through multiple steps of ideation, refinement and scheduling at a Team (aka Area) level prior to the VSO export occurring.