Stock filter ( quantity_and_stock_status ) is not displayed in layered navigation

[hiren-aimsinfosoft]

Preconditions (*)

1. Magento 2.4-develop
2. Display out of stock product in listing page

Steps to reproduce (*)`

1. Configure quantity_and_stock_status attribute according https://docs.magento.com/user-guide/catalog/navigation-layered-filterable-attributes.html#step-1-set-up-the-attribute-properties
   
   
2. Open any anchor category from the frontend
3. Attribute quantity_and_stock_status is not present in layered navigation

Expected result (*)

1. Attribute quantity_and_stock_status is should be present in layered navigation or 'Use in Layered Navigation' option should be disabled for this attribute

Actual result (*)

1. Attribute quantity_and_stock_status is not present in layered navigation
   

[m2-assistant]

Hi @hiren-aimsinfosoft. 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.

@hiren-aimsinfosoft do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @arushibansal013. 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[daweedco]

I have the same issue

[wb-magma]

I have the same issue

[sciola]

I have the same issue

[daweedco]

still no update ???

[m2-assistant]

Hi @engcom-Delta. 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-Delta
Thank you for verifying the issue. Based on the provided information internal tickets MC-38686 were created

Issue Available: @engcom-Delta, 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 @sdzhepa. 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.

[markhyng]

Hi @magento-engcom-team, which version or PR fix this problem?

[markhyng]

Hi @magento-engcom-team, any update?

[msyhr]

@magento-engcom-team also interested

[sdzhepa]

Updates for this issue:

This public issue report was closed by an automated system- bot which synchronized public and internal backlog.
It happened because internal ticket MC-38686 was closed with Wont Fix resolution
MC-38686 has a huge thread of comments and discussions and linked tickets
Summary and main statements:

• Functionality described in the issue and attribute(quantity_and_stock_status) related to Magento CatalogInventory module.
• CatalogInventory module was marked as deprecated since 2.3.0 release.
• Magento has a plan to remove CatalogInventory module in the nearest future
• Functionality will be reviewed and migrated/reimplemented from legacy CatalogInventory to MSI(Multi-Source Inventory).
• Problem described in issue Stock filter ( quantity_and_stock_status ) is not displayed in layered navigation #26172 is not trivial and requires solid development in the module that will be removed. Magento does not have plans to work on it but instead, this functionality will be re-considered in the scope of migration tasks.

That's all information that I found and can share now.

[TheRealHunzik]

I am facing this issue in Magento 2.3.4-p2 is there any solution?

[nordcomputer]

I created an extension, that sets a newly created attribute "filter_stock" to simple products according to the stock status via cronjob - its not a perfect solution, but it may help somebody:
https://github.com/nordcomputer/magento2-stockfilter

[Booqdan]

So there is any solution? From 2019 still not working?

[gfrey-namcopool]

Any update on this?