Full migration

[Yozya]

Hi.
We tried to full migration from one collection (XML process model) to another (inheritance process model). Version of Azure DevOps - 2019 Update 1.2.
Faced a lot of errors related to max size of attachments, "Work Item is not ready to save as it has some invalid fields" and related to config.
First question is do somebody did the full migration of all things that possible to migrate? If yes, could you please share your configuration file?

Second question is about an error. I saw a lot of errors like below but in "Project configuration -> Iterations" available the "Test-migration\Center" and "Test-migration\Management Team\Center To plan". I think that can be because of removed iterations paths. Can you confirm it? And can I somehow skip errors like this?

Thanks in advance!

Work Item is not ready to save as it has some invalid fields. This may not result in an error. Enable LogLevel as 'Debug' in the config to see more.
TfsExtensions::ToJson
Invalid Field Object:
{
  "WorkItemId": 276,
  "CurrentRevisionWorkItemRev": 3,
  "CurrentRevisionWorkItemTypeName": "Feature",
  "Name": "Iteration Path",
  "ReferenceName": "System.IterationPath",
  "Value": "Test-migration\\Center",
  "OriginalValue": "Test-migration\\Management Team\\Center To plan",
  "ValueWithServerDefault": "Test-migration\\Center",
  "Status": 16,
  "IsRequired": true,
  "IsEditable": true,
  "IsDirty": true,
  "IsComputed": true,
  "IsChangedByUser": true,
  "IsChangedInRevision": false,
  "HasPatternMatch": false,
  "IsLimitedToAllowedValues": false,
  "HasAllowedValuesList": false,
  "AllowedValues": [],
  "IdentityFieldAllowedValues": [],
  "ProhibitedValues": []
}

[MrHinsh]

What you may be hitting is a moved work item or a deleted area/iteration path. If a Work iTem previously was set to this area/iteration and then subsequently the area/iteration was deleted, then it would not be valid to add this in the history. Area/iteration paths are the one thing that we cant bypass the rules for.

There are two options to resolve this:

Option 1: Add the missing area/iterations

This can be enabled automatically by using the ShouldCreateMissingRevisionPaths to true in the TfsNodeStructureOptions of the CommonEnrichersConfig list.

Option 2: Map the missing area/iterations

Add a field map to map the missing area/iterations (map the expected target area/iteration to an existing area/iteration). Then set StopMigrationOnMissingAreaIterationNodes to false to continue with the migration.