Configurable product attribute issue

[Puru2016]

Preconditions (*)

1. Magento 2.3.1 with sample data
2. Size attribute Use in Layered Navigation

Steps to reproduce (*)

1. Log into the admin account.
2. Navigate to Catalog > Products.
3. In add new product dropdown choose configurable product and create a configurable product using “Size” attribute:-

3. Size attribute available to choose in configurable, but leave it as it is.
   Once you created the configurable product, size attribute also assigned to main configurable product like this:

3. Once you filter the products on category page using 49 size, this product visible in filter result. As I am not using 49 size in configurable product. (49 size are not available in my store).

Expected result (*)

1. Size attribute should not be assign to parent configurable product, so once user filter the product on category page using 49 size, this product not show in filter result.

Actual result (*)

1. 49 Size assigned parent configurable product automatically and visible in filter result on category page when user select size 49. That is wrong functionality.

Let me now if you need more explanation to understand this issue.

[m2-assistant]

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

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

[Puru2016]

I am only using Size 48.5 and 48.7 for create child products in configurable product.

Here is the Size attribute details:-

[m2-assistant]

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

[Puru2016]

Any update on this or require more information to replicate this issue, Please let me know.

[ghost]

I am also facing the same issue.

[magento-engcom-team]

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

[magento-engcom-team]

Hi @Zyles, here is your Magento instance.
Admin access: https://i-26449-2-4-develop.instances.magento-community.engineering/admin_3ede
Login: 51d66acd Password: 80ddfef013c1
Instance will be terminated in up to 3 hours.

[shikhamis11]

@magento give me 2.4-develop instance

[magento-engcom-team]

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

[magento-engcom-team]

Hi @shikhamis11, here is your Magento instance.
Admin access: https://i-26449-2-4-develop.instances.magento-community.engineering/admin_34c2
Login: c42e9552 Password: e7b88a189aa3
Instance will be terminated in up to 3 hours.

[m2-assistant]

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

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

[magento-engcom-team]

Hi @Puru2016. Thank you for your report.
The issue has been fixed in #27339 by @tna274 in 2.4-develop branch
Related commit(s):

• e7ff694959704cc0c570d330b70ee8c79855ad43
• 1071acfcea57b050d8ba432371455e2de09d723f
• 3b6b038c329178ec08d4202967edf1f19ab461f5
• 19ceb3a596f773bca9de0bcff1f75cf58df22563
• 1efecdfaaabeb6eaaef24e81bdb7c6579c589174
• 1e9895dfc62f7a2b9f241a83e9a6be979b44fa13
• d139cf93be642abb8a858af2cdd4bcb8fbf10cc0
• ec6bb304c1e8832c3079f2b2a4628098df370696
• 7cad47619fc39218f3b0fa5f178c7e9dd8defbea
• d89625934957ad1d61f9634a01e14a3b40b0ca9c
• 7d886585b058dfd0279e08da59185a75e6703d8c
• 43e7715093e5b59c026e99ed57fb22e85af6a712
• 784e73347f76d5d5e2984e4e81b3ee8f8ee29aeb
• 962274a69c81a078399b3c3fc2aa027f34ccbcf2
• ea414794ead14a83609cd19efcdaa4d6d9c14de2
• 14863006f3644fd892ed47fdbd1c310c3ea365c0
• deb55867d3faa7a7831cca7d9af77a6b8ffffa71
• dfb74d5287a6f39c4d3868635100c6df2622b23b

The fix will be available with the upcoming 2.4.1 release.