Wrong custom option title translations when creating order manually in Magento Admin

[antonioglass]

Preconditions and environment

• Magento 2.4.1
• Anything else that would help a developer reproduce the bug.
• Magento 2.4-develop with multiple website, and store.
• PHP 8.1

Steps to reproduce

1. Create multiple website, Store and Store view.
2. Create a product with custom options.
3. Translate custom options for 2 different store views.
4. Create an order via Magento Admin for store 2.

Expected result

Custom option titles must be the same as translated for a certain store.

Actual result

Custom option titles are taken from the first store.

Title translations when adding a product to order:

Title translations after product is added to order:

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 @antonioglass. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.4-develop instance with edition ee

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://14129224bada479b39ca50bc1771ef58.instances.magento-community.engineering
Admin access: https://14129224bada479b39ca50bc1771ef58.instances.magento-community.engineering/admin_0430
Login: ac18f976
Password: 3ccdd0c5b0ef

[engcom-Bravo]

Hi @antonioglass,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance but could not reproduce the issue.We are getting correct custom option title translations when creating order manually in Magento Admin.Kindly refer screenshots.

Steps to reproduce:
1.Create a product with custom options.
2.Translate custom options for 2 different store views.
3.Create an order via Magento Admin for store 2.

Kindly check the behavior on Magento 2.4-develop instance and provide missing steps if any if the issue is still reproducible.

Thanks.

[antonioglass]

Hi @antonioglass,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance but could not reproduce the issue.We are getting correct custom option title translations when creating order manually in Magento Admin.Kindly refer screenshots.

Steps to reproduce: 1.Create a product with custom options. 2.Translate custom options for 2 different store views. 3.Create an order via Magento Admin for store 2.

Kindly check the behavior on Magento 2.4-develop instance and provide missing steps if any if the issue is still reproducible.

Thanks.

Hello!

Thanks for working on this. I reproduced the issue on your Magento 2.4-develop instance.

1. Created additional store view.
2. Created a product "Product with custom options".
3. Added a custom option.
4. Translated a custom option for both store views.
5. Created an order via Magento Admin.

See screenshots below.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://14129224bada479b39ca50bc1771ef58.instances.magento-community.engineering
Admin access: https://14129224bada479b39ca50bc1771ef58.instances.magento-community.engineering/admin_24c7
Login: 207ff2b7
Password: d4a07e4ec474