Faulty revision - deleted iteration, migration error

[38224]

a revision in a work item set the iteration to one that does not exist anymore, and the migration goes to error.
"Work Item is not ready to save".

is there any way to bypass a failed revision? or do i need to recreate the iteration

[10:19:39 INF] ===============================================================
[10:19:39 ERR] Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF237124: Work Item is not ready to save
at Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItem.Save(SaveFlags saveFlags)
at MigrationTools.TfsExtensions.SaveToAzureDevOps(WorkItemData context) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\TfsExtensions.cs:line 77
at VstsSyncMigrator.Engine.WorkItemMigrationContext.ReplayRevisions(List`1 revisionsToMigrate, WorkItemData sourceWorkItem, WorkItemData targetWorkItem) in D:\a\1\s\src\VstsSyncMigrator.Core\Execution\MigrationContext\WorkItemMigrationContext.cs:line 685
[10:19:39 INF] ===============================================================
[10:19:39 DBG] TfsExtensions::SaveToAzureDevOps
[10:19:39 DBG] TfsExtensions::SaveToAzureDevOps: ChangedBy: X, AuthorisedBy: B
[10:19:39 WRN] 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.
[10:19:39 DBG] --------------------------------------------------------------------------------------------------------------------
[10:19:39 DBG] --------------------------------------------------------------------------------------------------------------------
[10:19:39 DBG] TfsExtensions::ToJson
[10:19:39 DBG] Invalid Field Object:
{
"WorkItemId": 22760,
"CurrentRevisionWorkItemRev": 1,
"CurrentRevisionWorkItemTypeName": "Feature",
"Name": "Iteration Path",
"ReferenceName": "System.IterationPath",
"Value": "A\_Requests F",
"OriginalValue": "A",
"ValueWithServerDefault": "A\_Requests F",
"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.