Customer Edit Issue when there is a newsletter queue associated with it.

[chichitsai0517]

Preconditions (*)

Installed a fresh copy of Magento 2.3.5-P2 with no sample data. Upgrade using composer to 2.4 (where we see the issue) and then upgrade to 2.4.1 (where issue is still present).

1. I tried on 2.4.0 and 2.4.1 and they both have the same issue.
2. Reproducible on 2.4-develop

Steps to reproduce (*)

1. Add a new customer which is also subscribed to newsletter.
2. Create a a newsletter in Marketing>Newsletter Templates
3. Queue the newsletter
4. Go to customer and try to edit their information - This is what we get (https://prnt.sc/v642qm)
5. Go create a new customer and subscribe to newsletter (however this new customer is not and has not been in any newsletter queue yet) - When we go and edit this customer, everything is ok (https://prnt.sc/v64460).

Expected result (*)

1. See Screenshot (https://prnt.sc/v64460)

Actual result (*)

1. See Screenshot (https://prnt.sc/v642qm)

[m2-assistant]

Hi @chichitsai0517. 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

[mohanelamurugan]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @mohanelamurugan, here is your Magento Instance: https://2c733cd0e59c58e896002eb77dbbdf01-2-4-develop.instances.magento-community.engineering
Admin access: https://2c733cd0e59c58e896002eb77dbbdf01-2-4-develop.instances.magento-community.engineering/admin_5997
Login: 2cd8a252
Password: 11ad61b8dbca

[mohanelamurugan]

Unable to reproduce this issue, Works fine on both 2.4 and 2.4.1

Steps followed:

• Create a new customer with newsletter subscription.
• Create a newsletter and queue it.
• Edit the customer created.

[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]

Hello @chichitsai0517

Thank you for your report

We confirm that we are able to reproduce the issue on 2.4.1

However, it is already fixed on 2.4-develop, and will be delivered in the next release

So we are closing this issue. Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines

Thank you

[engcom-Bravo]

Let's leave this issue opened until the 2.4-develop and 2.4.1 are synchronized

[chichitsai0517]

Is there a temporary solution to fix this until the next release?

[ioweb-gr]

It would be very helpful to know which commits fix it so that we can apply the patch on our crippled instances.

[engcom-Bravo]

After the 2.4-develop and 2.4.1 synchronization, the issue is reproducible on 2.4-develop also.
We confirm the issue and move it to Ready for Development

[m2-assistant]

Hi @engcom-Golf. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[fedekrum]

Is there a temporary solution to fix this until the next release?

Yes, there is if you don't care about the newsletter's queue. Erase it in the database by truncating newsletter_queue and problem solved.

[engcom-Bravo]

Is there a temporary solution to fix this until the next release?

#30727