Reorder in Admin panel leads to report page in case of changed product custom option max characters

[oleksii-lisovyi]

Preconditions (*)

1. Magento ver. 2.3.2-p2.

Steps to reproduce (*)

1. Configure a product with text (area) custom option, that has "Max Characters" value = 15.
2. Place an order with the configured product.
   2.1. The text custom option value should be at least 11 symbols length.
3. Change the value of the product text custom option "Max Characters" to 10 (or less).
4. Go to the placed order in Admin panel.
5. Click on "Reorder" button.

Expected result (*)

The Admin user see a clear error message, that explains, why the order couldn't reordered.
Probably it's enough to implement it in the same way as on frontend for registered customer:

Actual result (*)

The Admin user see a report page.

[m2-assistant]

Hi @oleksii-lisovyi. 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.

@oleksii-lisovyi do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[oleksii-lisovyi]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @oleksii-lisovyi. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @oleksii-lisovyi, here is your Magento instance.
Admin access: https://i-26345-2-4-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[oleksii-lisovyi]

I was able to reproduce the issue on the provided vanilla Magento instance.

[m2-assistant]

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

[m2-assistant]

Hi @cedmudit. 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!

---

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

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-30362 were created

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

[slavvka]

Hi @oleksii-lisovyi. Thank you for your report.
The issue has been fixed in #26348 by @cedmudit in 2.4-develop branch
Related commit(s):

• 16079d95e30cc6be2aa6a35b79f80db9e90ac155
• 86dc12d370a0b23d9dc04e9e5a7b7b1be78ccaf4
• a21b2466f6d63e5b9d120ff0295f80f51c2ec7cc
• 43f9e2b61dca391ca4c887f0c0c939dcbace34b7
• 7ba11b83fdfdccb65fbe097f3c51a267f09a7f24
• 6c5fbcb16196a5e7757fe82c77f358da3aae1678
• f7819a64af4ce9789fa86a71948870eaccbf8c95

The fix will be available with the upcoming 2.4.0 release.