Welcome to ShenZhenJia Knowledge Sharing Community for programmer and developer-Open, Learning and Share
menu search
person
Welcome To Ask or Share your Answers For Others

Categories

I've recently completed the deployment of TFS 2015 Update 1, we have around 15 development teams in the UK and previously we have always structured our TFS projects as follows:

Default Collection Application 1 (Team Project) Application 2 (Team Project)

This caused issues with sharing work items across teams as it is difficult to move WI's across the project boundary.

Rather than create a new team project for each team, I want to manage things with a single team project and create separate areasiterations eams for each one. So:

Project Collection > Master Team Project > Area 1 Area 2 Area 3 etc

in terms of permissions I would like to add in each of the standard TFS permission groups to each area. I would also like to create a root folder for source control for each area.

At the moment I can't work out how to do this? Can anyone help?

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
thumb_up_alt 0 like thumb_down_alt 0 dislike
139 views
Welcome To Ask or Share your Answers For Others

1 Answer

I suggest you to look at the some community suggestion on this topic.

In general it is a good practice (I won't say best practice as it is not the right thing to do in some cases).

Regarding you question, you should focus on Team to define developers access, and TFS groups for general (e.g. administrative) access.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
thumb_up_alt 0 like thumb_down_alt 0 dislike
Welcome to ShenZhenJia Knowledge Sharing Community for programmer and developer-Open, Learning and Share
...