2,382 votes152 comments · Azure DevOps (formerly Visual Studio Team Services) » Administration & Licensing · Flag idea as inappropriate… · Admin →
We are committed to supporting the ability to move projects between collections, however we’ve been unable to make progress on this feature. Unfortunately, the challenges highlighted in earlier posts are still present.
I don’t foresee us making progress on this feature within the next 6 months. We will provide an update once we start planning for the second half of 2019.
Azure DevOps Program Manager
pat and all readers:
this forum had been moved to a different forum Visual Studio Developer Community and archived and is not longer monitored by MSFT.
You can see the announcement when you go up one level in the forum.
@martin, TFS Integration Platform is far away from being an ideal solution for the described scenarios if you really want to migrate all data of a Team Project.
From Visual Studio Code Gallery "Team Foundation Server Integration Tools (March 2011 Release)":
As mentioned above, there are items that are not migrated when using the tool and this should to be taken into consideration when deciding on whether to do a migration or upgrade.
What IS NOT migrated by the Toolkit
* Check-in notes
your solution works only if you can live with a new Team Project Collection but not if you want to combine several Team Project from different Team Project Collections into a single Team Project Collections and therefore is almost unusable in real life
26 votes5 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
the exact same behavour exists in previous version of TFS Web Access.
27 votesDaniel Steiner shared this idea ·
1,067 votes37 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
Unfortunately we have had to make the decision to not bring the new Inheritance model to TFS on-prem with the next major release. It was a tough decision that we didn’t take lightly. The scope cuts that we had to make in order to deliver it to on-prem were just too painful, and would not give the User Experience we would be proud of.
We are still planning to bring it to our on-prem customers in a future release of TFS.
Sorry for not having a better answer.
VSTS/TFS Program Manager
same idea as this here "support upgrading to newer process template version for existing team projects"
why have the original author of this idea been overriden by VS ALM Team ?
replacing the original author also prevents update notification of this idea. I don't think that there're some real technical reason to replace the author when the visualstudioalm customer feedback had been merged into visualstudio customer feedback
29 votes1 comment · Azure DevOps (formerly Visual Studio Team Services) » Administration & Licensing · Flag idea as inappropriate… · Admin →
in principle the same idea as "make it possible to move a Team Project between Team Project Collections" http://visualstudio.uservoice.com/forums/121579-visual-studio-ideas/suggestions/2037613-make-it-possible-to-move-a-team-project-between-te
those two idea should be merged