'Tags' content cannot be migrated from TFS to DevOps by this tool

[FudongCa]

Discussed in #977

^{Originally posted by fudongma1970 July 23, 2021}
'Tags' content cannot be migrated from TFS to DevOps by this tool: the work item type could PBI, Bug, Task etc.

[MrHinsh]

Tags content is migrated. However, if you have a non-standard tag field name that does not match the target you will need to do a field mapping.

Older version of TFS may have this issue.

[FudongCa]

Tags content is migrated. However, if you have a non-standard tag field name that does not match the target you will need to do a field mapping.

Older version of TFS may have this issue.

Thanks for reply. Our TFS is Microsoft Visual Studio Team Foundation Server 2013, Version 12. Could this version has this issue?

[MrHinsh]

The version can be the issue here

[FudongCa]

Tags content is migrated. However, if you have a non-standard tag field name that does not match the target you will need to do a field mapping.

Older version of TFS may have this issue.

tags are in our TFS2013 instance, and storing under System.Tags

[FudongCa]

I have noticed that 'Tags' (and also 'Description') cannot be migrated, this is because of FIELD type related issue. In our TFS, the type of 'Tags' is PlainText, and type of Description is HTML. Looks like the migration tool cannot read values from Tags, description in TFS

[MrHinsh]

I have noticed that 'Tags' (and also 'Description') cannot be migrated, this is because of FIELD type related issue. In our TFS, the type of 'Tags' is PlainText, and type of Description is HTML. Looks like the migration tool cannot read values from Tags, description in TFS

Incorrect! These field types are migrated just fine. You have incorrectly configured the tool.

If the name of the fields between the locations do not match then it will not migrate. You need to add a FieldMap to the config to move the data from your TFS FieldRefName to the Azure DevOps FieldRefName..

[MrHinsh]

Tags content is migrated. However, if you have a non-standard tag field name that does not match the target you will need to do a field mapping.

Older version of TFS may have this issue.

Thanks for reply. Our TFS is Microsoft Visual Studio Team Foundation Server 2013, Version 12. Could this version has this issue?

Yes, it could be. You will need to check the field Refnames match. I have no idea which fields were changed in which version, but you can lookup inside your TFS and check the name in Azure DevOps.

[FudongCa]

OK. Now I have tried three different mappings for 'Tags' migration, and I also have 'successful' debug info.
However, I just cannot see the migrated 'Tags' info in Azure DevOps, target side. Please help.
By the way, I have checked the two fields Refnames match, System.Tags on both source and target.

"FieldMaps": [
{
"ObjectType": "FieldValueMapConfig",
"WorkItemTypeName": "",
"sourceField": "System.Tags",
"targetField": "System.Tags",
"valueMapping": {
"Est:Y": "Est:Y",
}
},
{
"ObjectType": "FieldtoTagMapConfig",
"WorkItemTypeName": "",
"sourceField": "System.Tags",
"formatExpression": "{0}"
},
{
"ObjectType": "FieldtoFieldMapConfig",
"WorkItemTypeName": "*",
"sourceField": "System.Tags",
"targetField": "System.Tags"
},

Output Debug Level Info:
2021-07-28 14:21:31.641 -04:00 [DBG] Running Field Map: FieldValueMap System.Tags System.Tags
2021-07-28 14:21:31.641 -04:00 [DBG] Running Field Map: FieldToTagFieldMap System.Tags
2021-07-28 14:21:31.641 -04:00 [DBG] Running Field Map: FieldToFieldMap System.Tags System.Tags
2021-07-28 14:21:31.642 -04:00 [DBG] FieldToFieldMap: [UPDATE] field mapped 19154:System.Tags to 55857:System.Tags
2021-07-28 14:21:31.642 -04:00 [DBG] Running Field Map: FieldToFieldMap Microsoft.VSTS.Common.DescriptionHtml System.Description
2021-07-28 14:21:31.643 -04:00 [DBG] FieldToFieldMap: [UPDATE] field mapped 19154:Microsoft.VSTS.Common.DescriptionHtml to 55857:System.Description
2021-07-28 14:21:31.643 -04:00 [DBG] TfsExtensions::SaveToAzureDevOps

[MrHinsh]

Fields that are the same on both sides are mapped automatically without a mapping.

You will need to debug in Visual Studio and see what this particular field is not mapping.

[FudongCa]

Fields that are the same on both sides are mapped automatically without a mapping.

You will need to debug in Visual Studio and see what this particular field is not mapping.

Thanks for your reply. Looks like the source value cannot be read. In the debug log, FieldToFieldMap: [UPDATE] field mapped ..., if you can include the source value and target value, I will be able to know that. Can you give me a compiled version of the tool that include both value in the debug info?

[swhitaker85]

i am also having this same issue, field names appear to be fine, but it wont copy. did you ever figure out a resolution?

[MrHinsh]

@FudongCa you can fork this repo and submit a PR.

[swhitaker85]

i am having the same exact issue from TFS to ADO, ive gotten every field to copy except tags.

[MrHinsh]

Which version of TFS?

[swhitaker85]

[swhitaker85]

apologies this is the version of VS i am using but the TFS web server is

I had to work around the issue for now by using the fieldtotag function, but this is not ideal and requires a lot of manual work. We are only in testing phase at this point.

[FudongCa]

I did not resolve that issue, ignored. Ma, Fudong

…

________________________________ From: Martin Hinshelwood nkdAgility.com ***@***.***> Sent: Wednesday, September 22, 2021 5:39:16 AM To: nkdAgility/azure-devops-migration-tools ***@***.***> Cc: FudongCa ***@***.***>; Mention ***@***.***> Subject: Re: [nkdAgility/azure-devops-migration-tools] 'Tags' content cannot be migrated from TFS to DevOps by this tool (Discussion #997) The version can be the issue here — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#997 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AU33HBXAHXHDPFI36SQBU63UDGP4JANCNFSM5EQOGX5Q>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.