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.
Work is still ongoing for our plan to enable an Organizations experience for Team Services. We will open up a private preview in 2017 H2 for interested customers to sign up to use this feature. I will provide another update when we are close to open up the private preview.
Program Manager – VSTS & TFS
Sven Lauterbach commented
+ for project collections
Giovanny Saray commented
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
Stephan van der Watt commented
Hi Team, any update on this? We desperately need this feature.
Is there any update on this feature.
Hi Microsoft, could you please share an update on this? thanks!
Martin Fletcher commented
Is there any update on when this feature will be landing?
Andreia Susano commented
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.
Miguel Isidoro commented
Is there a planned date for the release of this feature?
Ryan Miller commented
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 Tranter commented
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...
Jason Nichols commented
I just want to be able to rename the collection from 'default collection' to my domain name.
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$!
Yep Multiple Collections would make life much better. One collection is too simple even for limited development in a multi application environment
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)
Denis Oliva (tecsined) commented
We need this for distribute application and multiple independent teams
Or include 100% project separation within one VS Online Project Collection, for example by making it possible to assign a VS Online to selected projects (so, a User can have either "full scope access" within the entire Project Collection, or a User can be assigned to specific projects, preventing looking up anything outside those projects).
Larry Kloepping commented
+1 for grouping projects. I work in an enterprise with literally 100's of projects not being able to organize projects is a huge disappointment.
Bernhard Baumgartner commented
We really need the feature to organize our team projects in different collections on the same TFS server. We definitely won't use VS Online unless this feature is available. And I'm sure there are a lot of other developers that don't use VS Online due to the lack of this feature.
@Martin: I don't want to connect to different TFS servers for each customer according to your example. I want to stay connected to the same TFS server just switching between collections instead!
Martin- you are not creating multiple collections given your statement; you are creating multiple VSO accounts, each with a DefaultCollection. There needs to be the ability to have collections in addition to the DefaultCollection under a single VSO account as you can do in an on premises TFS installation. Microsoft's cloud based development infrastructure including Azure is not yet sufficient for complex organizations is all.
Martin Hinshelwood commented
I currently create multiple collections in VSO, one for each customer. Each collection gets a unique URL, so I create http://customer-nkd.visualstudio.com as part of my active directory infrastructure. This keeps the collection isolated from the other customers and gives me the option to 'hand over' the collection directly to the customer.
What features are lacking in this process?