Let us create multiple collections on Visual Studio Online
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.
This is a great idea! Although we plan to make this available to you in the near future, we are still in the planning process. We will check back as soon as possible with any updates to this request.
TFS Program Manager
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?
Hopefully this will be soon. do not want to move to sourcegear.
Graham O'Riley commented
Is there a due date for this feature?
We really need it now like all other companies.
Eduardo Cortés commented
+1 This is so necesary...
TFS is useless if you can't organize projects.
Hi, I will apreciate this feature to get ready on next VS Online version. This is very important.
Today, I come for look for this feature and it's not there. I'm stuck with the default collection. It's absurd.
Joe Vella commented
It is insane that at this point a feature so fundamental to organizing projects - internally or as a consultancy - has not been implemented by now.
Neil Hibbert commented
Yes please, this is a must have feature!
Michiel Lowijs commented
Please make this happen! We want to move our company TFS to the cloud.
Why have collections when you can't create new ones? That makes no sense at all. Please add this immediately!
I need it fastly too...
Due to the lack of this feature we have toyed around with running multiple instances of VS0. Although this makes management a little more difficult, in the end it closely mirrors multiple collections.
I would think that Microsoft would want to fix this considering that you get 5 free users for each VSO instance. That’s 5 licenses that I potentially would not need to purchase with multiple VSO’s compared to paying for them under a single instance.