Issues Found on Grid Multi-Select Column

[mahesh-rajawat]

Preconditions (*)

1. Magento 2.3-develop and Magento 2.3.2

Steps to reproduce (*)

Issue First:

1. Open any grid having some records.
2. Click on Header Checkbox to select all record on current page. https://prnt.sc/p09pr0
3. Now unselect some record, on click particular row: https://prnt.sc/p09pya
4. Again click on Header Checkbox, here is the issue.
5. Now you will see all records are unselected but header checkbox is selected. https://prnt.sc/p09qh6

Issue Second

1. Now Select the per page record to 1 https://prnt.sc/p09rfr
2. And select all record on current page by clicking header checkbox. https://prnt.sc/p09rrj
3. Go to second page you will see that the header checkbox is selected on all remaining pages.
   https://prnt.sc/p09s42

Expected result (*)

1. https://prnt.sc/p09qof

Actual result (*)

1. https://prnt.sc/p09qh6

[m2-assistant]

Hi @maheshWebkul721. 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.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

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

[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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[magento-engcom-team]

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

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

[emotaphp]

#mm19br

[magento-engcom-team]

@emotaphp thank you for joining. Please accept team invitation here and self-assign the issue.

[m2-assistant]

Hi @sudheers-kensium. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[m2-assistant]

Hi @prabhatrawat-webkul. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[shikhamis11]

#MM20IN

[sdzhepa]

Duplicate of #24348

[VladimirZaets]

Closed as a duplicate of #24348

[magento-engcom-team]

Hi @maheshWebkul721. Thank you for your report.
The issue has been fixed in #29968 by @engcom-Hotel in 2.4-develop branch
Related commit(s):

• 1f6e82fede343e6e239aaedc854ea6d63317272c
• e837bdc66501762a46418e2fdfea3746295f690f
• 591e04e80f0727840ac9ec8035caa055e148a930
• 8a9546f7f0a938a9752508fe6ffa090cd4d76f00
• f019712ea87afd04e7f6ec521f40f28c0894a8a5
• 4a20d6efc56b97e3ea73886b4a9ce51eefc322e2
• 70df4f05f74ecbb87355ac7c60fce6407436406b
• a85a63b7fb59ae7cf92c3c1a2dc65afe49fcba3d
• 462f12379f7a03c3acac35ff23e4295848bb0f24

The fix will be available with the upcoming 2.4.2 release.