Import customizable options adds it to another product if same SKU is filled

[DependencyHell]

When creating a new product, if by mistake I set the SKU of an already existing product, and import customizable options from this one, these options will be imported to the first product with same SKU, althougth an error shows that same SKU is existing.

Preconditions

Magento 2.1.5

Steps to reproduce

1. Create a simple product with customizable options (i.e SKU : product-test)
2. Create a product and set same SKU
3. Import customizable options from the first product
4. Save

Expected result

1. Information message indicates that SKU has been changed (should explain it is already in use)
2. Confirmation message indicates that Product is saved
3. Customizables options should be imported in this new product

Actual result

1. Information message indicates that SKU has been changed
2. Confirmation message indicates that Product is saved
3. Imported customizable options are saved to the already existing product that had SKU set first

First Product with sku 'product-test', and 2 customizable options :

Create a new product and by mistake set same sku 'product-test', then on Customizable Options click on Import Options :

Select first product, and click Import :

Everything looks fine, click on Save button :

Oops, by mistake I set an already existing SKU, the system changes it, no pb. I can leave happy.
Wait NO! Look at the bottom of the product page, check the new custom options, nothing!

Return to first product, used to import Customizable options, and here it is duplicated...

[Andrii-Deineha]

@DependencyHell Hi, thanks for reporting this issue. Internal ticket was created MAGETWO-70232.

[magento-engcom-team]

@DependencyHell, thank you for your report.
We've created internal ticket(s) MAGETWO-70232 to track progress on the issue.

[magento-engcom-team]

Hi @DependencyHell

This ticket has been marked as "Triage Wanted" due to low user involvement over time. Over the next 2 weeks we are looking for additional community feedback to decide if it should be archived or not. More information on this is available on the GitHub wiki.

Thank you for collaboration.

[magento-engcom-team]

@DependencyHell thank you for your report.

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

You may learn more about this initiative following this link.

Please feel free to comment or reopen the ticket if you think it should be reviewed once more. Thank you for collaboration.