magento/magento2#39640: Issue with the Customizable Options grid on the product page in the admin panel

[pavel77718]

Description (*)

As the author of the issue wrote, the problem is that when adding a new option in excess of the configured amount, the interface switches to the second page, but the new value is not added—the page remains in a constant loading state.

Fixed Issues (if relevant)

1. Fixes Issue with the Customizable Options grid on the product page in the admin panel #39640

Manual testing scenarios (*)

1. Go to the product page.
2. Create a Customizable Option with the drop-down type.
3. Add new values until both pages are fully populated.
4. Save the product.
5. Navigate to the Customizable Options tab.
6. Add a new value.

Expected result

The interface switches to the third page with the new value.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @pavel77718. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[pavel77718]

@magento run all tests

[pavel77718]

@magento run all tests

[pavel77718]

@magento run all tests

[pavel77718]

@magento run all tests

[pavel77718]

@magento run Functional Tests B2B, Functional Tests EE, Integration Tests

[pavel77718]

@magento run Integration Tests

[pavel77718]

@magento run all tests

[pavel77718]

@magento run all tests

[pavel77718]

@magento run Database Compare, Functional Tests B2B, Functional EE, WebAPI Tests

[pavel77718]

@magento run Functional Tests EE

[pavel77718]

@magento run all tests

[pavel77718]

@magento run Functional Tests B2B, Functional Tests EE

[pavel77718]

@magento run all tests

[pavel77718]

@magento run Functional Tests B2B, Functional Tests EE

[engcom-Hotel]

Hello @pavel77718,

According to this review comment #39694 (review), can you please add an automated test for this fix?

Thanks

[engcom-Dash]

Hello @pavel77718 I wanted to check if you are working on the automated test coverage. If not, Can I take care of them? Just let me know what works best for you.

[pavel77718]

I haven't started working on the tests. You can take care of that.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Static Tests, Unit Tests, Functional Tests B2B, Functional Tests EE

[engcom-Dash]

@magento run all tests

[engcom-Dash]

Hello @engcom-Hotel,

I have added the jasmine tests for the fix. Also , I feel that the failing test cases are not related to the PR changes. Could you please review it ? Moving this PR to pending review.

Thanks!

[engcom-Bravo]

Hi @pavel77718,

Thanks for the collaboration & contribution!

✔️ QA Passed

Preconditions:

• Install fresh Magento 2.4-develop

Steps to reproduce

• Go to the product page.
• Create a Customizable Option with the drop-down type.
• Add new values until both pages are fully populated.
• Save the product.
• Navigate to the Customizable Options tab.
• Add a new value.

Before: ✖️ 

Screen.Recording.2025-05-15.at.11.36.13.am.mov

After: ✔️

Screen.Recording.2025-05-15.at.2.32.14.pm.mov

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Functional Tests B2B, Static Tests

[engcom-Dash]

The consistent failure in Functional B2B is not related to the PR changes and it is a known issue. The other failure is inconsistent. They neither part of the PR nor failing because of the PR changes.

Build 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39694/b9fb336e413ec1f099994c29d2fa5bb2/Functional/allure-report-b2b/index.html#categories/8f0831c1d06562890f5ec21062dae309/c697e0409abfe9f8/

Build 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39694/c4347804b8cd14e8d042caeb57d833ec/Functional/allure-report-b2b/index.html#categories/8f0831c1d06562890f5ec21062dae309/6199b12ab001d804/

Known issue: StoreFrontSimpleProductWithSpecialAndTierDiscountPriceTest https://jira.corp.adobe.com/browse/ACQE-7971

Static Test Failure

The consistent static test failures are not because of this code changes done in this PR. In order to get the green build, We have raised an approval JIRA for static failures: https://jira.corp.adobe.com/browse/AC-14710

Once we get all the approvals we will move ahead with this PR. For now moving this PR to "Pending Approval"