Work item ID used in destination project breaks Parent/Child work items link.

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

Work item ID used in destination project breaks Parent/Child work items link. #32

Open bfbatch opened 6 years ago

bfbatch commented 6 years ago

Hi, I've successfully moved all work items and after creating and new team (same as source) and assigned rights all looked good. However, most iterations have an title group called "unparented" and in it are all the unlinked work items. After investigation it seems that the work ID was already used in the destination so a new work ID was created. This breaks the linking, is there a section I missed? If not any programatic way to relink?

jdshkolnik commented 6 years ago

I'm getting this as well, @sferg-msft

In today's migration, it created the related link correctly and then deleted it 7min later.

obvioussean commented 6 years ago

Were you using the latest version when you left this comment? About a month ago I updated link handling due to a change in VSTS.

jdshkolnik commented 6 years ago

Yes. It was latest at time of attempt.

brmdbr commented 5 years ago

Any update on this? I'm running into the same problem.

obvioussean commented 5 years ago

@brmdbr Could you please attach your logs?

mdrafiqsa commented 5 years ago

@obvioussean Work item number are not in sync with source TFS in VSTS? when I run my query it is returning expected result based on ID order starting from 1 . i am really not sure, since I am trying it for the first time?