Admin order emails send even when 'Email order confirmation' is unchecked

[github-jira-sync-bot]

Issue:
Admin order emails send even when 'Email order confirmation' is unchecked

 

Steps to reproduce:

• Create a customer account or register as a customer (for the purpose of creating an admin order).
• Go to Sales > Order and click on "Create New Order".
• Select the customer, add the products to the order, fill in the address, and select the Shipping and Payment methods.
• Before submitting the order, untick the "Email Order Confirmation" check box.
  
• Click on "Submit Order" to create the order.

Actual result:
An order confirmation email is sent regardless of the unticked "Email Order Confirmation" check box.

Expected result:
An order confirmation email should not be sent if the "Email Order Confirmation" check box is unticked while order creation.

Additional information:

• If we tick the "Email Order Confirmation" check box, two emails are sent to the customer.
• This checkbook state is being honored during the Invoice and Shipment creation, so this behavior in Order creation is inconsistent.

[github-jira-sync-bot]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1200

[m2-assistant]

Hi @github-jira-sync-bot. 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

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6831 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @o-iegorov. Thank you for verifying the issue.
Issue Available: @o-iegorov, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[ankitsrivastavacedcoss]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @ankitsrivastavacedcoss, here is your Magento Instance: https://95d4f577b0f1c93a301eae8c8086cc68.instances.magento-community.engineering
Admin access: https://95d4f577b0f1c93a301eae8c8086cc68.instances.magento-community.engineering/admin_3455
Login: 9766194b
Password: 4e9ded5f08cf

[chittima]

Internal team is working on this issue

[hostep]

Closed without a comment explaining why?

But it's probably fixed by https://github.com/magento/magento2/search?q=ACP2E-1200&type=commits ...

[chittima]

Issue is already fixed in the develop branch and not reproducible anymore. Here is the commit 1de1cea