Admin Grid selection issue - Magento 2.3.4

[JDhere]

Preconditions (*)

1. Magento Version 2.4.3.
2. Have some orders in sales order add.

Steps to reproduce (*)

1. Go to admin panel->Sales->Orders
2. Search for a particular increment id in the search bar.
3. Then the result of that order field will be displayed(1 result).
4. Select the rendered result.
5. Now search for another increment id in the search bar
6. Select the displayed result
7. Clear all the filters
8. It will move to the original grid view, now all the checkboxes will be deselected

Expected result (*)

1. The grid should select only the selected result and keep all other fields unchecked.

Actual result (*)

1. When the admin grid is rendered after removing the filters it deselects all the selected orders

PS

As discussed in the comments,
The issue is recreated in a different way in the latest magento release.

Magento Version: 2.4.3-p1

Steps to reproduce

1. Go to Sales->Orders
2. In the grid copy a increment id and paste it in the search field and perform search operation.
3. Now select the record(only 1 will be displayed)
4. Now remove the filter
5. Now the selected record will be removed

Expected result

While removing the filter the selected record which was selected in the search operation should also be selected.

Actual Result

The selection is removed when the filter is removed.

Reproduced in Magento 2.4.x:

And as discussed in the comments that this is not a bug and its the intended method, we need a solution to fix this or improvise this in future.
Consider the use case scenario:

The user is changing the status of order by referring to his list.

The user opens the admin panel-> Then searches for an increment id-> Selects it-> Then again searches for an increment id-> selects it-> This goes on till his list is completed

Then he is performing the mass action eg: hold.
So in this case the purpose of mass action will itself get failed with the current bug!

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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 @JDhere. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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.

🎥 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

[JDhere]

@magento give me 2.3.4 instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @JDhere, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

[m2-assistant]

Hi @ajijshekh123. 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-November]

Hi @JDhere ,
Verified the issue on Magento 2.4-develop branch but cannot able to reproduce the issue. Sales Orders Grid is displayed without check boxes selected after removing the Increment ID filter applied. Kindly verify the issue on Magento 2.4-develop branch and provide missing steps if any if the issue is still reproducible.
Thank you.

[m2-assistant]

Hi @engcom-November. 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.

[JasonTychons]

@magento give me 2.4-develop instance

[magento-deployment-service]

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