Duplicating a product should copy the meta data in all stores

[cptX]

Preconditions and environment

• Magento version 2.4.8-p3

First of all this issue here is a bug report and a feature request at the same time.

Bug report:
Duplicating a product populates the meta data in the other stores views but not in the default store view

Feature request:
According to this unfortunate request #26054, magento doesn't anymore copy the meta data during duplication. This is a wrong decision and I really don't understand how it passed through the development!

This is very very wrong!!!! I'm losing so much time everyday because of this!!!

When duplicating a product you expect to get a duplicate, the definition of duplicate is to have all data the same!
Now when I'm duplicating a product I need to open an older product in another window in order to copy the metadata from it!!!! It is stupid!
It's better to duplicate the data and whoever doesn't want them just delete them, than having to open the older product in another display or browser just to copy these fields. The effort is enormous if you have many similar products. Whoever thought to suggest this spent so many hours of our lives... Please let's make it as before...

Steps to reproduce

Make 2 store views for example greek and english.
Create a product and fill in all the meta fields in both store views.
Make a duplicate of the product (From button Save & Duplicate)
The default view will not have the meta data populated, but the second view will have the meta data populated which in my opinion is the correct.

Expected result

I expect all store views to copy the metadata from the original product.

Actual result

Only the secondary store views copy the meta data from the original product, and the default view is not copying it.

Now in order to solve this, everytime I duplicate a product, I have to open another browser window, open the original product and copy one by one the meta description and meta keywords

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @cptX. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.