[Bug]: FieldtoFieldMultiMap & FieldMergeMap dont work anymore in 16.3.2-Preview.7

[MicE44]

Version

• I confirm that I am using the latest version

Source Version

Azure DevOps Service

Target Version

Azure DevOps Service

Relevant configuration

The tool ignores it in this version. [16.3.2-Preview.7]
No errors in the Logs.

In Version [16.2.11] it works as expected.

Its the same json file.

Relevant log output

[14:47:47 DBG] [16.2.11] FieldtoFieldMultiMap:  [UPDATE] field mapped 4929:Custom.AuftragsnummerMF2 to 6029:Custom.PO_Number
[14:47:47 DBG] [16.2.11] FieldtoFieldMultiMap:  [UPDATE] field mapped 4929:Custom.Charge to 6029:Custom.Lot_Number
[14:47:47 DBG] [16.2.11] FieldtoFieldMultiMap:  [UPDATE] field mapped 4929:Custom.Potential to 6029:Custom.ScrapAvoidance
[14:47:47 DBG] [16.2.11] FieldtoFieldMultiMap:  [UPDATE] field mapped 4929:Custom.Verantwortlich1 to 6029:Custom.Responsible1
[14:47:47 DBG] [16.2.11] FieldtoFieldMultiMap:  [UPDATE] field mapped 4929:Custom.VorgangNr to 6029:Custom.ReferenceCode
[14:47:47 DBG] [16.2.11] FieldtoFieldMultiMap:  [UPDATE] field mapped 4929:Custom.Wiedervorlagedatum to 6029:Microsoft.VSTS.CMMI.CalledDate

What happened?

A bug happened!

Debug in Visual Studio

• Visual Studio Debug

[nkdagility-actions-bot]

Hi there,

ACTION REQUIRED

In order for us to help you will need to provide both the log, and the configration file that you are using.

Generate and Attach Log

Steps:

1. In the Config file, change LogLevel to Debug.
2. Identify a work item ID that exhibits this issue and create a query that only selects this work item.
3. Delete any existing copy of that work item from the target.
4. Run the migration.
5. Comment here with the full Log attached as well as the full (redacted) configration file that you are using.

Your assistance is greatly appreciated!

Thanks, Azure DevOps Migration Tools team

[nkdagility-actions-bot]

Please create a GitHub Discussion instead of this issue.

As this issue has been labeled as needs-discussion by a maintainer it is being automatically closed and locked. It will later be deleted to avoid polluting repository searches with duplicate or incorrect content.

This doesn't necessarily mean that what you've reported isn't a problem or a reasonable idea, but it does mean that it should be raised as a Discussion first and not an Issue. Please create a Discussion now, assuming you still wish to discuss it.

Thanks, Azure DevOps Migration Tools team