[Clone MC-35417]Radio buttons are not displayed in the “Payment & Shipping Information” section in the case of reorder by Admin

[magento-engcom-team]

Preconditions:

• Magento EE 2.3.6, EE 2.3.7-alpha2
• A Customer account with shipping address and a billing address is created
• A Simple Product is created
• Several delivery methods are configured
• At least one order is created

Steps to Reproduce:

• Go to Magento Admin panel > Sales > Orders
• Select the created order
• Click the “View” link
• Click the “Reorder” button
• Scroll down the page to the “Payment & Shipping Information” section
• Click the “Click to change shipping method”

(/) Expected results:

The list of delivery methods with radio buttons should appear

(see the attached EE 2.4.1-alpha4. ADMIN REORDER RADIO BUTTONS EXPECTED.png)

(x) Actual results:

The list of delivery methods without radio buttons appears

(see the attached  EE 2.4.1-alpha4. ADMIN REORDER RADIO BUTTONS ACTUAL.png
                                  EE 2.4.1-alpha4. ADMIN REORDER RADIO BUTTONS.mp4)

[magento-engcom-team]

The issue was exported from the internal JIRA. The link to the original JIRA issue: https://jira.corp.magento.com/browse/MC-37373

[m2-assistant]

Hi @magento-engcom-team. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

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

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[magento-engcom-team]

✅ Confirmed by @magento-engcom-team
Thank you for verifying the issue. Based on the provided information internal tickets MC-37373 were created

Issue Available: @magento-engcom-team, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[AndreyChorniy]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @AndreyChorniy. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @AndreyChorniy, here is your Magento Instance: https://e28b75d0cbca1b51a554e02440625727-2-4-develop.instances.magento-community.engineering
Admin access: https://e28b75d0cbca1b51a554e02440625727-2-4-develop.instances.magento-community.engineering/admin_ca16
Login: 8e3088ca
Password: b0bde04d8479

[AndreyChorniy]

@magento I am working on this

[gabrieldagama]

Hi @magento-engcom-team. Thank you for your report.
The issue has been fixed in #32393 by @gixid192 in 2.4-develop branch
Related commit(s):

• 1be4239ba7f5fd512e6a51f386404883022ad513
• e40e45796a54e04ccf381d72a4d255bed98887e4
• b54b8524d662f746453a406aecc9ad83ac79b711
• 7dee9d8f64e3d05b0dee60dd7e7cad4620f5f2e6
• 2821bc189bd7aefc877d25180bcc870044aa60fe
• a57b22b86f51cf460030169c89fc592462dab89b

The fix will be available with the upcoming 2.4.3 release.

[jellesiderius]

Patch fix can be done like this: https://magento.stackexchange.com/a/347147/7855