Quick Search feature in Admin is not working properly when choosing in Products

[addison74]

Please see the image bellow:

Search in Admin for emma leggings then choose in Products, in Orders, in Customers, in Pages. All are providing results correctly, except in Products. If you choose "emma leggings" in Products you will get all products listed. This option has an issue providing correct results.

[choukalos]

Tracked as (MAGETWO-36855) internally when we apply the new enhanced data grid to products. Sales, Customer and CMS are the new enhanced data grids.

[magento-engcom-team]

Hi @addison74
Issue seems to be already fixed in the 2.3.0-dev with the PR #10089.
We will consider backporting it into previous versions.

[magento-engcom-team]

@addison74, thank you for your report.
The issue is already fixed in develop branch
But we will consider to backport the fix to patch releases

[magento-engcom-team]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[ghost]

Hi @addison74, The issue was re-tested and we can confirm that it was fixed on the 2.3 release branch. We closing this issue as fixed due to upcoming 2.3 release that will be available soon.