We have moved from A single collection with many team projects, to a single collection, with one team project, and just many source control folders (One for each project).
For each project we are going to use areas/teams to split things down logically.
However, we expect The Business who aren't TFS users will log bugs and such, via the correct team.
I have assigned default areas for the correct teams, and at some point in the move, we were able to view a team via web access, create a new Work Item, and it would use the correct Area.
For whatever reason this has now stopped - is there something I need to set to make sure it uses the correct/default area for the team?
You can configure the default area for each team in the Control Panel in the Web Access of your Team Foundation Server.
You should go to:
Control panel --> <your collection name> --> <your project name> --> <team name>
In the Areas tab you will see the hierarchy of the root project with all the teams beneath it. Make sure that the correct team is selected as the default area.
You can find the documentation here at MSDN: Add and modify area and iteration paths
I finally got this working by making sure the Team Name had no spaces This was the key and area have no spaces
Before one of our teams was Web Reports with an area Web Reports, nothing worked.
Changing the Team and Area to WebReports, and also marked the WebReports area as the default team for that area, and things started working.
Related
I'm relatively new to developing with tfs (only used git before).
I'm connecting to a server, which contains a decent amount of projects.
When I create a new work item, I can select only the server below 'classification' and not the specific project.
How can I allocate a work item directly to a project instead of the server?
Thanks!
You could directly create work item under the specific team project. The simplest and effective way is through web portal.
Project--Work--New Work Item--Work Item Type
After this the a work item directly allocated to this project instead of the server.
In work item, several features depend on the team project or team that
you have selected. For example, dashboards, backlogs, and board views
will change depending on the context selected.
When you add a work item, the system references the default area and
iteration paths defined for the team context. Work items you add
from the team dashboard (new work item widget) and queries page are
assigned the team default iteration. Work items you add from a team
backlog or board, are assigned the team default backlog iteration.
You navigate to your team context from the top navigation bar.
If you are new to tfs work item, suggest you take a look at related tutorial in MSDN: Plan and track your project with work items. Besides in TFS, there is a concept of permission, also make sure your account have enough permission for the project and adding work item.
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 areas\iterations\teams 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?
I suggest you to look at the some community suggestion on this topic.
One Team Project to rule them all
Why You Should use a Single (Giant) TFS Team Project
How to implement a multiple team strategy in Team Foundation Server 2013
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.
I'd recommend you to use the multiple teams feature in TFS2015. It allows you to manage the team members, permissions, work items more easily. And you can track the entire project status from the team project page and track the individual feature team status from their own project page. The work items can be also moved between the teams easily (Just change the area path). Refer to this link for details: Multiple Teams
We are using TFS 2010 and use work items and the changesets that are linked to them as the unit of change that gets deployed. I would like to put a work item into a "frozen" state, preventing any new changesets from being linked to it. Is this possible?
You can't lock individual Work Items so your best bet would be to set security on a particular area path and remove edit permissions to Work Items in that area for the required users.
When a Work Item is frozen it is put into that area and normal contributors wouldn't have access to edit it.
Team Foundation Server 2010 Permissions
You can set these permissions by right-clicking the project in Team
Explorer, clicking Areas and Iterations, and on the Area tab, clicking
Security.
The boards: Work/Backlog/product backlog/board(the stories/backlogitems) and on Work/board(tasks) can we have different column mappings per teams? Currently the type - value pairs are stored in CommonConfiguration, so it is project based, can we change it to be Team relative?
This totally depends on which update you are on (if you are using on-premise TFS). If your TFS deployment is Update 2 or higher - or you are using TFService - you can customize the "Kanban Board" (the board that shows work items on the backlog), link here: http://blogs.msdn.com/b/bharry/archive/2013/02/01/customizable-kanban-swim-lanes.aspx. This allows you to change the columns, per team, without changing the workflow of work items themselves.
As for the Task board, you can customize it, but only for an entire team project. This must also be done via the CommonConfiguration file.
I am considering moving from FogBugz to TFS 2012 for our bug/defect tracking. In FogBugz it's easy to create areas such as Database, Reports, etc. I went to the work items area and it had one that matched the project name. I created children of that to match our different teams. I later decided to add teams in TFS (I'm new to TFS, a lot to figure out!) so it created work areas to match the teams. So now I have:
ProjectName
--Blah
--Blah Team
--Foo
--Foo Team
Now I want to go back and delete Blah and Foo because it is foolish and confusing the way it is now.
How can I delete these work item areas I no longer want?
Thank you.
Go to team web access then right-click the items you no longer want and a context menu will appear with options such as delete.