Open
Description
Preconditions (*)
- Magento 2.4.2
- Elasticsearch 7
Steps to reproduce (*)
- Create a simple product, set visibility to catalog/search and url_key to 'simple'
- Create a bundle product, set visibility to catalog/search and url_key to 'bundle'
- Assign the simple product to the bundle product.
- Reindex so products are set in elastic
- Request the following GraphQl call:
Note: This issue observed for Grouped Product as well. If simple product is assigned to Grouped product and searching using url_key eq: simple product url_key returns both Simple and Grouped product
query products {
products(
filter:{
url_key:{
eq:"simple"
}
}
){ items {
url_key
}
}
Expected result (*)
"data": {
"products": {
"items": [
{
"url_key": "simple",
}
]
}
}
}
Actual result (*)
{
"data": {
"products": {
"items": [
{
"url_key": "bundle",
},
{
"url_key": "simple",
}
]
}
}
}
The Issue
Bundle product index many of their children's attributes. But it is also indexing the url_key. Which means that bundle products match, when filtering on url_key, on their own url_key and on the url_key of their children. This shouldn't happen because the only relevant url_key for the bundle is its own url_key.
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”.