Configurations actions merge decides based on first attribute

Description

When merging 2 XML files with configurations actions it was found that it duplicates elements that were constructed e.g. like this with default action COMPLETE:

Both of these elements would end up being duplicated after running When the order of attributes was switched (so that NAME was first) it produced correct results without the elements being duplicated.

It should work both ways since order of attributes does not matter in XML.

Environment

None

Assignee

Zdeněk Vaník

Reporter

Zdeněk Vaník

Impact

Functional - may break existing environments

Components

Sprint

None

Fix versions

Affects versions

Priority

Medium
Configure