Close date set as the migration time

[jessicafac]

Describe your issue:

A lot of WI has been migrated with the close time set as the migration data time, most of them Task type.

I would like to know if there is already a solution for this problem, either in the configuration, or if it is something that is being corrected for other versions.

migration time 30/01/2023

version. 12.0.36

[MrHinsh]

If the Source ClosedDate is empty then the Target Closed Date would be the date of the migration.

Can you check to see if the Source data is in-tact?

[jessicafac]

Log closedDate ok

closedDate migration time

[MrHinsh]

Well something is going on.

[MrHinsh]

Can you share a sanitized config?

[jessicafac]

config.txt

[MrHinsh]

Two things @jessicafac:

1. Update to the latest version of the code. Version 12 was from Feb 8 and there have been 50+ fixes shipped since then. I cant guranteee that this was not a bug fixed since then.
2. Remove all of the FieldMaps and try again!

[t-anderson]

My Agile Boards teams are also reporting this behavior. We see this on some migrated work items, but not all.

1. In query results we see either:
   'Closed Date' as migration datetime and 'Closed By' as migration user
   'Closed Date' as migration datetime and 'Closed By' as Source 'Closed By'
   'Closed Date' as Source 'Closed Date' and 'Closed By' as Source 'Closed By'

2. On the History Graph we see the correct Closed Date (Source 'Closed By')

3. On the revisions we see Resolved by as migration user

version 14.2.2

[t-anderson]

wiMigration-config.json
We are only using Regex field maps for the Area path and Iteration path fields. When removing these field mappings, the migration run throws an "Invalid Field Object: Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF237124: Work Item is not ready to save" error on these fields.

[MrHinsh]

First these are not going to work and should be deleted:

 {
      "$type": "RegexFieldMapConfig",
      "WorkItemTypeName": "*",
      "sourceField": "System.AreaPath",
      "targetField": "System.AreaPath",
      "pattern": "sourceProjectName\\\\",
      "replacement": "targetProjectName\\"
    },    
    {
      "$type": "RegexFieldMapConfig",
      "WorkItemTypeName": "*",
      "sourceField": "System.IterationPath",
      "targetField": "System.IterationPath",
      "pattern": "sourceProjectName",
      "replacement": "targetProjectName"
    },
    {
      "$type": "RegexFieldMapConfig",
      "WorkItemTypeName": "*",
      "sourceField": "System.IterationPath",
      "targetField": "System.IterationPath",
      "pattern": "sourceProjectName\\\\",
      "replacement": "targetProjectName\\"
    }

[MrHinsh]

I dont see anything else in the config that would be an issue.

Have you tried rerunning specific work items that have issues in Debug with Visual Studio to see whats up?

[t-anderson]

I sanitized the pattern and replacement strings for upload, but they are successful in our migration runs.

2023-11-22 08:42:36.848 -06:00 [DBG] FieldValuetoTagMap: [UPDATE] field tagged 885168:System.AreaPath to 0:System.AreaPath with regex pattern of sourceProjectName\\ resulting in targetProjectName\ProgramName\FeatureTeamName
2023-11-22 08:42:36.848 -06:00 [DBG] Running Field Map: RegexFieldMap System.IterationPath System.IterationPath
2023-11-22 08:42:36.848 -06:00 [DBG] FieldValuetoTagMap: [UPDATE] field tagged 885168:System.IterationPath to 0:System.IterationPath with regex pattern of sourceProjectName resulting in targetProjectName\ProgramName\PI 23.1
2023-11-22 08:42:36.848 -06:00 [DBG] Running Field Map: RegexFieldMap System.IterationPath System.IterationPath
2023-11-22 08:42:36.848 -06:00 [DBG] FieldValuetoTagMap: [UPDATE] field tagged 885168:System.IterationPath to 0:System.IterationPath with regex pattern of sourceProjectName\\ resulting in targetProjectName\ProgramName\PI 23.1

When removing these field mappings, the migration run throws an "Invalid Field Object: Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF237124: Work Item is not ready to save" error on these fields.

[MrHinsh]

It looks like you are using an old version of the tool. However, I have never seen Area or Iterations mapped with a field map. 🥇

Area and Iterations that match the source and target project are replaced by the system internaly and do not require mappings. Area or Iterations from 3rd projects (moved work items) do need a mapping, using the built in Area nad Iteration mappers.