Out of Stock products does not display on 2.3.0 also

[HEALTHYHOOKAHCA]

Preconditions (*)

1. Magento 2.3.0

Steps to reproduce (*)

1. Go to Admin side .. from left menu.. Stores >> Configuration >> Catalog >> Inventory
   In that, check "Stock Options" tab, in which I've set "Display Out of Stock Products" to "Yes", for all my views, website view, in default settings.
2. on Customer side, I can not see my all the products(Configurable Products). "Out-of-stock" configurable products are still missing.
   Like, I've one configurable product(Jam bottle), which has 12 flavors.
   Now, some of the flavors are not in stock. So these flavored products are not displaying on customer side.

Expected result (*)

1. All the flavors should be there in the dropdown list, see the image.
   
   I can see only 10 of them right now, there should be 12 flavors in the list.
   the flavors not appearing here are having 0 quantities. So they are out of stock proudcts.
   Technically they should appear here as on admin side the flag is set to "Yes" for Out of stock products.

Actual result (*)

on Customer side, I can not see my all the products(Configurable Products). "Out-of-stock" configurable products are still missing.
Like, I've one configurable product(Jam bottle), which has 12 flavors.
Now, some of the flavors are not in stock. So these flavored products are not displaying on customer side.

[magento-engcom-team]

Hi @HEALTHYHOOKAHCA. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

@HEALTHYHOOKAHCA do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[HEALTHYHOOKAHCA]

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

[magento-engcom-team]

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

[magento-engcom-team]

Hi @HEALTHYHOOKAHCA, here is your Magento instance.
Admin access: https://i-20780-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[HEALTHYHOOKAHCA]

I get the same issue on this instance also..
Please check it out

[magento-engcom-team]

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

• 5. 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

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

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

• 5. 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

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[shikhamis11]

@HEALTHYHOOKAHCA Thank you for reporting this issue .. as I can see yes the configurable options which are out of stock not displaying on frontend even the configuration is enabled . but I think this is done deliberately for config products options .. if the optional product has visibiliy catalog-search or search It can be accessed directly by opening in url .
so lets wait for someone for magento team to decide whether it is issue or not

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.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!

• 5. 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

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[ghost]

Hi @HEALTHYHOOKAHCA thank you for you report, this is acknowledged issue please look here -> #10454
@shikhamis11 thank you for explanations.