Github issues were incorrectly closed and need to be re-opened

[diamondavocado]

Posting this here because there's no other visible way to provide feedback or to contact the "moderators" of this repository.

Two issues have been incorrectly closed and at least one of them needs to be re-opened as they are still valid bugs in Magento 2.4:

1. CE 2.1.7 Attributes - Display Out of Stock Products #10454 was closed because @engcom-Charlie could not reproduce the issue. However the issue is still present. They need to try reproducing the issue using the suggestions posted in the thread (using configurable product with only one configurable attribute). See CE 2.2.X Configurable product with 1 Attribute - Display Out of Stock Products #15047 below for more info.

2. CE 2.2.X Configurable product with 1 Attribute - Display Out of Stock Products #15047 was closed because a now-deleted account said it was a "duplicate" of CE 2.1.7 Attributes - Display Out of Stock Products #10454, above. It may be the same issue but it is not a duplicate; it provides the instructions which @engcom-Charlie asked for; i.e. test a product with only one configurable attribute.

Some common sense is all that's needed here!

As a Magento 2 developer I am finding it incredibly frustrating to work on this platform, finding bug after bug after bug, and then coming to this Github to find that bugs have been closed for the wrong reasons! It's maddening.

[m2-assistant]

Hi @diamondavocado. 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.

@diamondavocado 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.

[ihor-sviziev]

@diamondavocado thank you so much for raising these issues again!
In both cases author of the issue should be able to re-open the issue if he/she not agree with person who tested it.

Were you able to reproduce this issue on test instance?
Will you be able to update this issue description with all needed details? Also I believe it's really hard to understand issue without screenshots / video. Will you be able do add some?

Update: I just reviewed the issue descriptions once again - 2nd one decription looks more clear. I'll just re-open it and close this one

[ihor-sviziev]

@diamondavocado I've re-opened #15047 and tried to reproduce it. Seems like this is expected result how it works right now.

Could you review my comment #15047 (comment) and give your feedback?

I'm closing this issue.

[m2-assistant]

Hi @ihor-sviziev. 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.