Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page encompasses our ninja team's 2 projects we brought over from TFS to DevOps. Please feel free to make edits, suggestions and improvements. Credit goes to John Sewchand (Unlicensed) for doing the research and legwork on the first one, and leaving instructions to follow for subsequent migrations.

Instructions

NOTE:  With this process you lose Iteration Path, Area Path, Assigned To, State, Reason, attachments and some other data.  This will have to be updated manually if desired.

  1. Export from TFS into Excel (https://docs.microsoft.com/en-us/azure/devops/report/excel/create-status-and-trend-excel-reports?view=azure-devops-2019)

    1. In TFS, create a query of the items you would like exported. Here is the query we used for CORAL.

    2. In Visual Studio, open Team Explorer, Work Items and navigate to the query created in step 1a. Right-click and select "Open in Microsoft Excel". Save it. Done.

  2. Import to DevOps (https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/office/bulk-add-modify-work-items-excel?view=azure-devops)
    1. Open a blank Excel sheet, hit the TEAM menu, then New List.
    2. Add the server: https://dev.azure.com/TCMarineSafetyOrg and click Connect.
    3. Enter user credentials (john.sewchand@034gc.onmicrosoft.com).
    4. Selected Input List.
    5. Hit the TEAM menu, Add Tree Level, select Parent-Child, then Convert.
    6. From the exported sheet, copy the values from the Work Item Type column into the new sheet.
    7. State and Reason automatically populate.
    8. Copy the Title 1 and Title 2 from the export sheet.
    9. Copy the remaining header values from the export sheet to the new one.
    10. Delete the duplicated Assigned To and Reason columns.
    11. Copy the data from the additional columns to the new sheet.
    12. Save the sheet and hit Publish.
      1. It may complain about Area Path, Iteration Path if they don't exist in Devops. Changethose to \.
  3. Open TFS and DevOps side by side, and manually move over any desired Attachements, Linked items, etc. that aren't covered by steps 1 and 2




  • No labels