NodeStructureEnricher.NodePathNotAnchoredException when a revision deals with story or bug moved between ado projects. #1693
-
NodeStructureEnricher.NodePathNotAnchoredException when a revision deals with story or bug moved between ado projects. 2023-10-24 15:30:05.824 -05:00 [DBG] PopulateWorkItem:FieldUpdate: System.AreaPath | Old:StrategicPod New:TotalView |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 19 replies
-
As per the documentation, you need to add Iteration Maps and Area Maps that adapt the old locations to new ones that are valid in the Target. Before your migration starts it will validate that all of the Areas and Iterations from the Source work items revisions exist on the Target. Any that do not exist will be flagged in the logs and if you have Our algorithm that converts the Source nodes to Target nodes processes the mappings at that time. This means that any valid mapped nodes will never be caught by the
To add a mapping, you can follow the documentation with this being the simplest way:
Or you can use regular expressions to match the missing area or iteration paths:
If you want to use the matches in the replacement you can use the following:
If the olf iteration path was Regular expressions are much more difficult to build and debug so it is a good idea to use a regular expression tester to check that you are matching the right things and to build them in ChatGTP. NOTE: You need |
Beta Was this translation helpful? Give feedback.
-
TV-configuration4-V1-wit-step-4-safe.json Still having the problem even with the mappings I have include json file and log file I will also include what debug information I could get. during the exception: This exception was originally thrown at this call stack: Call Stack
|
Beta Was this translation helpful? Give feedback.
-
I'm having a very similar problem as rpbalbrecht. There is an Area and an Iteration that doesn't seem to exist any more, but it's referenced in some work items and it derails the whole migration for that interval of time (we're doing year-by-year migrations). It's called "GFM-IC" and I can't get the mapping or any exclusions to work. I don't have access to the source ADO project, other than the PAT for permissions. We've migrated about 30,000 Work Items so far, and there are another 20,000 on the way, because I've narrowed it down to a week during one year (and I just migrated everything in that year except that one week so far), and I'm still looking for the culprit week in one of the other years. This is 10 years' worth of migration. Great tool, by the way. We've got Pipelines migrated, Work Items migrated (mostly), and I'll do the Test Plans next. I manually imported all the Repos through the DevOps portal. Here's my CommonTools setup. Let's say my source ADO project is called "SourceProject" and my target ADO project is called "TargetProject". Where would those go in the configuration below, if at all? And my trouble Area & Iteration is called "GFM-IC" and its children. Thanks!
|
Beta Was this translation helpful? Give feedback.
It worked with the "CommonTools" settings I posted above. I mean, I'm not 100% certain why it worked this time when I thought it errored out with those exact settings. It may have been that I thought I was referencing an updated JSON with the right settings when I actually wasn't. And it does take 5 minutes of running before erroring out and I've got tons of other things going on and sometimes I lose track of where I am.
Thank you so much, @MrHinsh, for providing some feedback as you did. I've learned so much over the past few days and I appreciate it greatly!