Work item names are not visible after migration

[naveengitdev2]

Discussed in #1598

^{Originally posted by naveengitdev2 July 20, 2023}
Q1) We have migrated over 5300 work items between different organisations in Azure devops. Post migration, some of the work item names are not showing and are blank in the target environment. Also all of these has work item state as New.

Q2) Can we migrate work item of any state together by editing parameters WIQLQueryBit?

What are the changes we need to make in the configuration.json file?

Below is our config file

{
"ChangeSetMappingFile": null,
"Source": {
"$type": "TfsTeamProjectConfig",
"Collection": "https://dev.azure.com/sourceorganizationame",
"Project": "sourceproject",
"ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
"AllowCrossProjectLinking": false,
"AuthenticationMode": "Prompt",
"PersonalAccessToken": "",
"PersonalAccessTokenVariableName": "",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
"Target": {
"$type": "TfsTeamProjectConfig",
"Collection": "https://dev.azure.com/targetorganizationame",
"Project": "targetproject",
"ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
"AllowCrossProjectLinking": false,
"AuthenticationMode": "Prompt",
"PersonalAccessToken": "",
"PersonalAccessTokenVariableName": "",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
"FieldMaps": [
],
"GitRepoMapping": null,
"LogLevel": "Information",
"CommonEnrichersConfig": null,
"Processors": [
{
"$type": "WorkItemMigrationConfig",
"Enabled": true,
"ReplayRevisions": true,
"PrefixProjectToNodes": false,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQueryBit": "AND [Microsoft.VSTS.Common.ClosedDate] = '' AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan')",
"WIQLOrderBit": "[System.ChangedDate] desc",
"LinkMigration": true,
"AttachmentMigration": true,
"AttachmentWorkingPath": "c:\temp\WorkItemAttachmentWorkingFolder\",
"FixHtmlAttachmentLinks": false,
"SkipToFinalRevisedWorkItemType": true,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": true,
"PauseAfterEachWorkItem": false,
"AttachmentMaxSize": 480000000,
"AttachRevisionHistory": false,
"LinkMigrationSaveEachAsAdded": false,
"GenerateMigrationComment": true,
"WorkItemIDs": null,
"MaxRevisions": 0,
"UseCommonNodeStructureEnricherConfig": false,
"StopMigrationOnMissingAreaIterationNodes": true,
"NodeBasePaths": [],
"AreaMaps": {},
"IterationMaps": {},
"MaxGracefulFailures": 0,
"SkipRevisionWithInvalidIterationPath": false,
"SkipRevisionWithInvalidAreaPath": false
}
],
"Version": "13.0",
"workaroundForQuerySOAPBugEnabled": false,
"WorkItemTypeDefinition": {
"sourceWorkItemTypeName": "targetWorkItemTypeName"
},
"Endpoints": {
"InMemoryWorkItemEndpoints": [
{
"Name": "Source",
"EndpointEnrichers": null
},
{
"Name": "Target",
"EndpointEnrichers": null
}
]
}
}

Any help would be appreciated. Thanks!

[naveengitdev2]

Hi Community,

Kindly request anyone to help us on this issue.
Update : We are able to migrate 5600 work items to target using the tool post doing some changes, but post migration some of the work item names/title are not visible in the target environment. Do we need to modify any script or add anything?

Attached screenshot for reference for the work items.

When we click on the work item, we get below output

Any help will be appreciated on this.

[MrHinsh]

This is a configuration issue. Change SkipToFinalRevisedWorkItemType to false.

[MrHinsh]

So the migration tool migrates field to field as long as it has the same name.

Check that the fields in the source have the same refname each side.

[naveengitdev2]

Thank you for your response. Can you please clarify on what you mean by the fields in the source have the same refname each side?

As of now, we have checked that the column name in the process are same for source and target environment.

[MrHinsh]

The system matches fields based on the Refname of the field:

Also its possible there could be issues with text in other languages that we may not have tested for.

The system loops through each field and copies the data to the matching field on the target side. If you are getting empty titles then that's weird!

After you check the above I would suggest running the migration from the code in visual studio and seeing where the data is being lost.

[MrHinsh]

Please note that I have not use "SkipToFinalRevisedWorkItemType": true, for a migration myself and cant latest to its validity.

[naveengitdev2]

thank you, now the names/titles are getting migrated after set options for the field as required. Had below 2 queries

1. Some of the links are getting skipped, below is one of the error. Is there a way to migrate work items first and then migrate the links afterwards using the same configuration file.

Migrating link for 4812 of type RelatedLink
[17:44:57 INF] [SKIP] Unable to migrate link where Link of type System.LinkTypes.Hierarchy-Reverse where wiSourceL=4812, wiSourceR=4753, wiTargetL=31870, wiTargetR=4753 as target WI has not been migrated

2. Getting below argument exception as it says item with the same key has already been added. How can we avoid this below exception.

ArgumentException
System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary2.Insert(TKey key, TValue value, Boolean add) at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer`1 comparer)
at MigrationTools.Endpoints.TfsWorkItemConvertor.GetRevisionItems(RevisionCollection tfsRevisions) in D:\a\1\s\src\MigrationTools.Clients.AzureDevops.ObjectModel\Endpoints\TfsWorkItemConvertor.cs:line 44

Thanks

[MrHinsh]

1. Work Items that are no migrated yet cant be linked to. However when the other side of the link is migrated it will be added automatically.

2. Thats a bad error that will need debugging. Is it reproducing consistently? You could try debugging a work item with this issue in Visual Studio and see why its jamming up.