Controls defined in separate project WIT's are seen as same field/merged

[Niffbert]

So, it seems that when using this extension it cannot separate value domains used for the same field in different team projects.

We've implemented the multivalue form control for a field that gets its values from GlobalListA:

<FIELD name="MyField" refname="MyNamespace.MyField" type="String">
        <SUGGESTEDVALUES expanditems="true">
                <GLOBALLIST name="GlobalListA" />
        </SUGGESTEDVALUES>
</FIELD>

<ControlContribution Label="My Field" Id="ms-devlabs.vsts-extensions-multivalue-control.multivalue-form-control">
        <Inputs>
                <Input Id="FieldName" Value="MyNamespace.MyField" />
        </Inputs>
</ControlContribution>

Now I wanted to change the valueset to GlobalListB for one of our projects, so I changed in its WIT definition and imported. The unexpected result was that the allowed values are now both global lists combined and not only that - it has changed to this value set for ALL projects in the collection, not only the one for which I updated the WIT.

We're using Azure DevOps 2019 Server (Version Dev17.M153.3) and version 2.2.26 of the extension.