How can we improve Visual Studio Team Services (VSTS)?

Let us create multiple collections on Visual Studio Team Services

As an organization with 25+ developers and 15+ ongoing/supported projects for several customers, we need the ability to group our team projects into different project collections.

I am sure we are not the only ones.

1,035 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thomas KalveThomas Kalve shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    114 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Martin FletcherMartin Fletcher commented  ·   ·  Flag as inappropriate

        My company is currently in the process of evaluating vsts and this feature would be a major swing factor for justifying vsts.

        How can I sign up for the private preview to evaluate this feature.

      • Brad LeachBrad Leach commented  ·   ·  Flag as inappropriate

        I want to be in the Private Preview too. We are planning our migration to VSTS. We have 2 on-prem servers. I've read the migration guide. I want to see how naming & URLs sort out as I migrate our 2 main collections.
        At this point, I created one account - <company>.visualstudio.com. Can I create another "account"/URL while still logged in with my same Visual Studio subscription? I don't see a way to do it.

      • Almiro AlvesAlmiro Alves commented  ·   ·  Flag as inappropriate

        Hi guys, I need much this, because in my company, we have several ares of bussines differences. So, I'd like organizate per "collection".

      • Giovanny SarayGiovanny Saray commented  ·   ·  Flag as inappropriate

        My company with 200+ developers and 50+ stakeholders is in the process of move the TFS OnPrem to Team Services. We are interested in the private preview of this feature. Please let us know when is ready, thanks

      • Andreia SusanoAndreia Susano commented  ·   ·  Flag as inappropriate

        This ir really a problem. In our organization we have more or less 15 projects and a distributed team of 10 elements, it's really difficult to plan sprints and to know if someone it's overlocated or not. I also think we need a point of view from the resource. Each team member should be able to see his own work from all projects.

      • Ryan MillerRyan Miller commented  ·   ·  Flag as inappropriate

        Currently using VSO for greenfield project&team... but need to migrate from on-prem TFS2008 and team to VSO... having issues with needing multiple releases/sprints running in parallel for the different projects. This may solve that?

        We do have shared code between projects as well.

        Solution is needed to have all teams/projects in VSO but allow different process templates and/or Release/sprints while RETAINING the ability for a single developer to have a single pain of glass to see all outstanding work across all of the VSO team projects.

      • Chris TranterChris Tranter commented  ·   ·  Flag as inappropriate

        this is causing us massive issue. i need a collection per region. the fact that there's a default collection infers others can be created...

      • Anonymous commented  ·   ·  Flag as inappropriate

        TFS Program Manager says "This is a great idea!". WOW, if you had "DefaultCollection" surely it comes across your mind at some stage it's a must-have feature to allow users to create multiple collections? And from a technical point of view, how difficult can it be to do such a simple thing?
        COME ON M$!

      • SBSB commented  ·   ·  Flag as inappropriate

        Yep Multiple Collections would make life much better. One collection is too simple even for limited development in a multi application environment

      • KG2VKG2V commented  ·   ·  Flag as inappropriate

        I'll add another +1. With multiple in house projects, AND multiple clients, each with many projects, the ability to group a client's projects is critical. May make us move to inhouse (we have the license)

      ← Previous 1 3 4 5 6

      Feedback and Knowledge Base