-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Low stock report showing disabled products #26838
Comments
Hi @Zyles. Thank you for your report.
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:
For more details, please, review the Magento Contributor Assistant documentation. @Zyles do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
Hi @engcom-Delta. Thank you for working on this issue.
|
✅ Confirmed by @engcom-Delta 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. |
Hi @Mohamed-Asar. Thank you for working on this issue.
|
Hi @Zyles. Thank you for your report. The fix will be available with the upcoming 2.4.0 release. |
The low stock report becomes pretty useless pretty fast unless you delete products. We store disabled product for history and the chance that they may come back in stock.
There is no way to do a report and filter out the disabled products.
This means you have to go through A LOT of non-active products in the low stock report which makes it completely unusable.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Either remove the disabled products from the report or have the ability to filter them out.
Actual result (*)
Unable to remove disabled products or filter them out. Making the report useless since there are a lot of old products that don't need to be reviewed for low stock.
The text was updated successfully, but these errors were encountered: