Can someone please supply a super simple WIT migration configuration file that actually works with 16.3? #3020
-
|
I'm using this tool since forever and its never been more exhausting to try use this for a very simple WIT migration. I know about reflectedworkitemid field, I know about impossibility of moving Test Plans, I don't need fancy regex invocations, I don't care about GIT repos - just simple TFS -> AzureDevOps work item migration. Ok. Enough crying. For example, https://devopsmigration.io/docs/get-started/getting-started/ the given basic configuration.json doesn't work. When you put TFS/ADO info, PAT creds, no fancy mapping - tool fails before starting: [16:04:05 ERR] [16.3.1] Configuration file 'new.json' is not valid against the schema. Validation errors (deduplicated & filtered): Likely root cause missing properties (all deduped candidate sets): Path: MigrationTools.Processors[0]
Total unique validation errors after filtering: 3 Why default config simply doesn't work? What it is missing? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 15 replies
-
Things change over time, and not all the documentation keeps up. Would love a PR with that change; otherwise, it will be updated as someone gets around to it. This tool is supported by its contributors and creator with no remuneration. |
Beta Was this translation helpful? Give feedback.
-
|
@EdPerminas - I just succeeded with a test migration from on prem devops server 2022 using this config... obviously used real secrets etc.. Quick additional comment - i ran the migration from my "on prem" server logged in as an account with solid permissions in the on prem server. I wasn't prompted for anything - and execution stopped when running right when i would expect to be prompted for something - i simply pressed enter and migration started... This is as basic as any configuration gets i assume... (this is my first attempt with the tool - so i am about as fresh as you can get to this tool) |
Beta Was this translation helpful? Give feedback.
-
|
@EdPerminas - yeah - maybe the use of IntegrationBuild is a problem... When i run the migration multiple times, i am not getting any added items from source to target... Not sure if it should be possible to get updated items, but I am at least not gettinga any... |
Beta Was this translation helpful? Give feedback.
This is the error that's stopping it. The validation failed. Check out https://devopsmigration.io/docs/reference/tools/work-item-type-validator-tool/