Solving https://github.com/magento/magento2/issues/34758

[iwanzijderveld]

Preconditions and environment

Solving #34758

Steps to reproduce

Solving #34758

Expected result

I can't wrap my mind around why this issue that is marked as priority S0. Which states "A problem that is blocking the ability to work. An immediate fix is needed" is still not solved after almost 4 years. It feels like this issue has been overlooked for some reason.

Actual result

Solving #34758

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 @iwanzijderveld. 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.

[engcom-Bravo]

Hi @iwanzijderveld,

Thanks for your reporting and collaboration.

This #34758 issue has been already confirmed with P1 priority and JIRA is in Implementation and we will discuss with Internal Team and provide updates soon there.

Thanks for your Understanding Hence we are closing this issue.