How can we improve Team Services?

make it possible to move a Team Project between Team Project Collections

Currently you need to move an existing Team Project to a new Team Project Collection. I would like a feature to move Team Project between Team Project Collections without using TFS Integration Toolkit or other 3rd party tools.

2,817 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Visual Studio ALM TeamVisual Studio ALM Team shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared a merged idea: make it possible to move projects and move history as well  ·   · 
    planned  ·  Visual Studio TeamAdminVisual Studio Team (Product Team, Microsoft) responded  · 

    Enabling the ability move projects between collections is a definitely a feature that we want enable. It’s currently on our product backlog, but it is not in our 6 month plan. We will provide an update once we start planning for the second half of 2016.

    Rogan Ferguson
    TFS Program Manager

    39 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • David HokeDavid Hoke commented  ·   ·  Flag as inappropriate

        We need this as a dependency to migrate our on-prem TFS projects to new collections within VSO. Existing tools let us migrate to the root of VSO but we can not move code to collections from there without losing history, branching, etc. Consequently, we can not use VSO for complete ALM as we hoped. We want to get this migration done so we can start using Release Management in a fully integrated manner as well. The new features are in our critical path.

      • Randy in MarinRandy in Marin commented  ·   ·  Flag as inappropriate

        We have TFS onsite. I considered going to VS Online, but we don't have the ability to move our collection there and back. Having the ability to move a team project to and from the cloud will make it a lot easier for us to make the jump.

        I hope the transfer is designed to be compact and efficient - and not via millions of web service calls. An additional backup/restore option at the team project level? (Move the team project to a private collection, make the compressed backup, transfer, restore, move the private collection to a target collection? Or perhaps moving a team project is a special case of split collection and combine collection?)

      • Randy in MarinRandy in Marin commented  ·   ·  Flag as inappropriate

        It is good news that this feature will be added someday. I would think a measure of success would be the ability of moving a project there and back again without a loss of functionality or information. I hope the implementation of moving team projects will be done in a manner compatible to other potential future features. For example, it might also be nice to combine 2 or more team projects into a single project (as subfolders?). Move the project (a subfolder?) back out?

      • Steinar HerlandSteinar Herland commented  ·   ·  Flag as inappropriate

        This tool should also make it possible to move source and pbi's++ from on-premise TFS to Visual Studio Team Services

      • Sherrill DarbySherrill Darby commented  ·   ·  Flag as inappropriate

        Archiving team projects using the TFS Integration Tool works but does not help when you have literally thousands of test cases which also need to be migrated. We need a tool to move the team project with all assets.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Currently users are able to move projects inside TFS between distinct team projects, but if for some reason we make a move and after that we delete the original team project, then the history of moved projects is totally lost. So it would be great to move and preserve history with move independently of what happens to the previous location of moved files or projects

      • Bill SimpsonBill Simpson commented  ·   ·  Flag as inappropriate

        A recent reorganisation request to move projects around collections to make it simpler for our company to record support issues for all our applications from one place, would require this feature to be implemented

      • Shawn McNabbShawn McNabb commented  ·   ·  Flag as inappropriate

        I can add our voice to this request as well. We recently moved to 2013 and need to separate projects by business units. Plus we have many projects that can be archived. It looks like all movement on this has stopped. We would rather not use third party tools to augment the functionality of TFS. If the ability to migrate collections can't easily be built in, why can't Microsoft can provide a tool?

      • Bart JansonBart Janson commented  ·   ·  Flag as inappropriate

        Note, when moving a team project, all data should be removed from the source collection (not just the versioning files, but also all work item data).

        I created a separate uervoice story after finding out that during a split, not all project data is removed.

        https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/6775719-clean-up-all-workitemdata-in-the-database-for-a-de

      • Andrew BarkerAndrew Barker commented  ·   ·  Flag as inappropriate

        TFS Collections are great for organizing projects by the teams responsible, I just wish that I could easily move projects between collections to indicate when a project has been assigned to a new team or has been archived.

      • Vik JaggiVik Jaggi commented  ·   ·  Flag as inappropriate

        We'd like this feature too. Right now folks have to muddle through an array of tools to migrate the data and still a lot of it is lost. Why can't MS make it easier for everyone and provide a tool to do it?

      • Randy in MarinRandy in Marin commented  ·   ·  Flag as inappropriate

        This is one of the major failings of the current TFS design. Having a single changeset sequence for a collection limits options. I think a changeset sequence per team project would have been better. Perhaps every team project needs a globally unique guid. A single checkin would generate a new sequence number in every team project that is part of the checkin. A new collection method would be required to simulate a collection changeset sequence. Perhaps a table that relates the team project changesets? The collection level sequence would change as projects are exported or imported, so using it as a key would not be good. Stable references would have to use the team project guid (or id mapped to the guid - I don't like guids) and team project changeset number.

        Perhaps another option is to use a universal time to the nanosecond instead of an integer sequence. When moving team projects around, the changeset values will mostly merge. If the some changeset times are the same, introduce a tracked change to make them unique. When exporting the team project, undo any changes used to make records unique. (Add a ns? Add a fraction of a ns? Add a sequence id column that is normally 0?)

        Without a redesign, it will be close to impossible to move projects correctly without re-sequencing changesets. That does not sound fun at all. A TFS 2016 with a new design could import an old collection and add new team project sequences just by using the old values. After that, projects are free to roam.

      • Michael DynesMichael Dynes commented  ·   ·  Flag as inappropriate

        This is a very relevant feature/functionality. I currently have a need to migrate a development project from TFS 2010 collection instance to a TFS 2013 collection instance. Currently, that does not appear to be possible.

      • Anonymous commented  ·   ·  Flag as inappropriate

        The ability to move a project and/or consolidate collections is a capability that needs to be addressed. TFS Intergration tool is/was not the answer.

      • Eric AldingerEric Aldinger commented  ·   ·  Flag as inappropriate

        I would like this feature as well. I have had several occasions to do this and it is less fun than other tasks in TFS

      • Suman BrarSuman Brar commented  ·   ·  Flag as inappropriate

        This would definately be a very useful feature as it will help in solving the database size issues. By moving a particular project to new collection, bloating datatbase size will reduce and help in overall backup, maintenance and upgrades.

      ← Previous 1

      Feedback and Knowledge Base