Problem Description
Customers often ask me: "? In Azure DevOps Server, how to migrate a project team to another team project collection."
The simple answer is: " the current version does not support !."
This is currently the world's highest degree of concern a user needs ( https://developercommunity.visualstudio.com/idea/365365/make-it-possible-to-move-a-team-project-between-te-1.html ), but it is very regrettable, Microsoft product groups currently can not solve this problem.
problem analysis
In fact, in view of the Azure DevOps Server (TFS called before) the design, upgrading can not be achieved within a short time this function through the system. There are many reasons this can not be achieved features, but the core of which is a unique data marker ID.
In TFS system, all work items have a unique ID value, the ID value is automatically incremented by a serial number 1, for example, a new ID requirements for 1001, after a new Bug work item ID is 1002 . In a project team with the set, the serial number of the work item ID is shared, that adds a work item in a team project in the first, the second new team project work item ID also It adds one automatically. In a different team project, it is possible there are 1001 such work items. If we migrate between the project team team project collection, the work item data will become very confusing.
In addition, because the traditional TFVC library also has the same problem, the same team project collection, the path is to begin with the dollar sign ($), format file path is "$ / team name / file or folder path" If we migrate between the project team team project collection, data will also make the system becomes chaotic.
Coupled with the complexity of the data structure of the reporting database tfs_warehouse in, making this migration becomes very complex, involving data change too much, almost an impossible task.
Therefore, we do not ask how the future migration of the project team.
solution
From the above analysis, we can see that this is a problem without a solution.
However, we can avoid this problem. In order to avoid the process of using Azure DevOps Server migration issues need to appear in a team project, the need for R & D data in the enterprise is a good program to use in the beginning, to create a team project according to certain criteria. For example, with a product line of information systems to store the same set of project team, the same team of R & D information systems to store the same team project collection; considering the thousands of project team does not appear, try using the default the team project collection (DefaultCollection), avoid the use of a new team project collection.
------------------------------------------------------------
http://www.cnblogs.com/danzhang/ DevOps MVP Zhang Hongjun
------------------------------------------------------------