Filtering configurable product by availability of related simple products doesn't work.

[mgroensmit]

Preconditions (*)

1. Magento 2.4-develop
2. Configuration value for 'Display out of stock products' is set to 'no'
3. Configuration value for 'Backorders' is set to 'no backorders'
   

Steps to reproduce (*)

1. Create a configurable product with two configurable attributes. In the example I used the Magento sample data with the 'color' and 'size' options.
2. Set one of the simple products to be out of stock, and set the rest to be in stock.
3. Filter the product listing on the frontend and select the filters for both the configurable attributes to values that should result in the configurable product being out of stock.

Expected result (*)

1. The product doesn't show up in the listing.

Actual result (*)

1. The 'olivia 1/4 light zip jacket' in the screenshot below is not available with the combination of 'size xs' and 'color purple', but it shows up in the listing when the filters are applied.
   

---

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 @mgroensmit. 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.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, 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

[mgroensmit]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @mgroensmit. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @mgroensmit, here is your Magento instance.
Admin access: https://i-29166-2-4-develop.instances.magento-community.engineering/admin_d4ce
Login: a9344479 Password: 9f683b042459
Instance will be terminated in up to 3 hours.

[mgroensmit]

Issue is reproducible on Magento 2.4

[m2-assistant]

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

[magento-engcom-team]

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

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

[m2-assistant]

Hi @engcom-Kilo. 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.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!
• 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.

[engcom-Kilo]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @engcom-Kilo. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @engcom-Kilo, here is your Magento instance.
Admin access: https://i-29166-2-4-develop.instances.magento-community.engineering/admin_c9ec
Login: 879bfd77 Password: 13731613a1a3
Instance will be terminated in up to 3 hours.

[tgamanov]

Hello @mgroensmit.
Trying to reproduce the described issue and not able to do it.
Please have a look at the gif

and provide more additional information.
Thank you in advance.

[mgroensmit]

Trying to reproduce the described issue and not able to do it.

@tgamanov the issue is with the filtering in the layered navigation, not with the swatches in the listing. If you apply the filters for both color and size and select a combination of values that is not available, you will still see the product in the listing as long the color or the size filter don't individually filter the product.

In my example in the original post, the 'Olivia' jacket is not available in the combination 'xs' and 'purple', but it still shows up in the listing when those filters are set because there are other color options available for the 'xs' size and other size available for the color 'purple'.

The swatches do reflect the 'out-of-stock' status of this product, but this issue is nevertheless problematic because configurable products can be created with attributes that are not swatches, giving no visual indication to the out-of-stock status of the product on the Category View page.

[tgamanov]

Hello @mgroensmit.
I got your point. Let me check it.
Thank you for the additional information.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[magento-engcom-team]

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

Please feel free to comment or reopen according to the Issue reporting guidelines
the ticket if you are still facing this issue on the latest 2.x-develop branch. Thank you for collaboration.

[matthewhaworth]

I think this is still an issue.

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @matthewhaworth, here is your Magento Instance: https://5f828c1208d4b1ba8f40f0a870edac96.instances.magento-community.engineering
Admin access: https://5f828c1208d4b1ba8f40f0a870edac96.instances.magento-community.engineering/admin_65aa
Login: c0a406cf
Password: 50dc1e48f485

[matthewhaworth]

Curious to see if this used to happen with the MySQL adapter in 2.3, or whether it's elasticsearch causing it as per #20593

@magento give me 2.3 instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @matthewhaworth, here is your Magento Instance: https://94ffb0755ad1621daa5d5c4418adcbcb.instances.magento-community.engineering
Admin access: https://94ffb0755ad1621daa5d5c4418adcbcb.instances.magento-community.engineering/admin_355b
Login: 314e0f5a
Password: d2523cfe3288