Re-linking test work items

microsoft / vsts-work-item-migrator

WiMigrator is a command line tool for migrating work items between VSTS/TFS projects

MIT License

148 stars 69 forks source link

Re-linking test work items #4

Open jdshkolnik opened 6 years ago

jdshkolnik commented 6 years ago

The migrator will bring over test plans, suites, and cases, but it won't relate them to each other correctly because they are not linked like other work items. For example, a test case created independently won't appear in a test suite even if that suite is linked as the parent.

This is known behavior but the migrator is of limited utility without some means to migrate the test work item relationships. I took a quick look at the REST API but didn't see anything which could be used to solve this. Any ideas? @sferg-msft

obvioussean commented 6 years ago

As you noticed, there are no APIs available today to make the migrator work for test work items. I will dig around to see if there is anything I can do to make it possible.

mjcarrabine commented 4 years ago

I'm not sure about APIs required to update these links on the Target, but the new v3 oDATA APIs at least are exposing the links on the Source.

We have been using these new APIs in PowerBI to identify failed test cases that have bugs that are closed and can now be retested. Since there does not appear to be a way to create a query with these links.

Here is an example using the new API https://docs.microsoft.com/en-us/azure/devops/report/powerbi/sample-test-plans-tester-by-outcome?view=azure-devops&tabs=powerbi

Xerxes0198 commented 2 years ago

Hey, I am experiencing this, too. Does anyone know of a good strategy for migrating Test Plans, Suites and Cases with their structure in tact?