Skip to content

Grid search selectall issue #29968

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

engcom-Hotel
Copy link
Contributor

Description (*)

Fix for selecting all on the grid during the search by keyword and select all on-page toggle after unchecked records.

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes magento/magento2#<24348>
  2. Fixes magento/magento2#<24400>

Manual testing scenarios (*)

  1. UI Component grid indicates a wrong number of selections when removing keyword search #24348
  2. Issues Found on Grid Multi-Select Column #24400

Questions or comments

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)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Sep 9, 2020

Hi @engcom-Hotel. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ 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

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

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

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please 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

@engcom-Hotel
Copy link
Contributor Author

@magento run all tests

@gabrieldagama gabrieldagama added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Severity: S1 Affects critical data or functionality and forces users to employ a workaround. labels Sep 10, 2020
@gabrieldagama gabrieldagama self-assigned this Sep 10, 2020
Copy link
Contributor

@gabrieldagama gabrieldagama left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @engcom-Hotel, thanks for your pull request, it looks great, please have a look on my comments below:

gabrieldagama
gabrieldagama previously approved these changes Sep 10, 2020
Copy link
Contributor

@engcom-Alfa engcom-Alfa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @engcom-Hotel .

During testing, we faced the issue.

Manual testing scenario:

  1. Select all records on the current page by clicking the header checkbox;
  2. Go to the second page;

Actual Result:

✖️ you will see that the header checkbox is selected on all remaining pages

Peek 2020-09-11 09-51

@engcom-Hotel Could you take a look?

Thanks!

@ghost ghost dismissed gabrieldagama’s stale review September 11, 2020 07:11

Pull Request state was updated. Re-review required.

@gabrieldagama
Copy link
Contributor

@magento run all tests

@magento-engcom-team
Copy link
Contributor

Hi @gabrieldagama, thank you for the review.
ENGCOM-8175 has been created to process this Pull Request
✳️ @gabrieldagama, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@gabrieldagama gabrieldagama added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Sep 14, 2020
@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Case 1.

  1. Open any grid with more than 1 page (Customers for example);
  2. In the 'Search by keyword' box, enter '[email protected]' and search;
  3. In the first column, choose the 'Select All' option
  4. Notice that one record is selected:

2020-09-15_10-07

  1. Remove the '[email protected]' keyword search by pressing the 'x' icon to the right of it.

Before: ❌ It is shown that one сcustomer is selected but in fact, all entries in the grid are selected

Peek 2020-09-15 10-14

After: ✔️ Now when we clear the search filter all the checkbox marks in the grid are also removed

Peek 2020-09-15 10-10

Note: applied the same behavior as filters have.

Screenshot from 2020-09-15 10-23-38

Case 2

  1. Click on Header Checkbox to select all records on the current page;
  2. Now unselect some record, on click particular row;
  3. Again click on Header Checkbox;

After: ✔️ all records are unselected and the header checkbox is unselected.

Peek 2020-09-15 10-42

@engcom-Alfa
Copy link
Contributor

The new ticket #29996 has been created for the issue described in the comment as it was not caused by changes in this PR.

@engcom-Alfa engcom-Alfa added the QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope label Sep 15, 2020
@engcom-Charlie engcom-Charlie self-assigned this Sep 15, 2020
@engcom-Charlie
Copy link
Contributor

@magento run all tests

@engcom-Hotel
Copy link
Contributor Author

@magento run all tests

1 similar comment
@gabrieldagama
Copy link
Contributor

@magento run all tests

@m2-assistant
Copy link

m2-assistant bot commented Sep 19, 2020

Hi @engcom-Hotel, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: Customer Component: Ui Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S1 Affects critical data or functionality and forces users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants