Skip to content

Configurable product attribute issue #26449

Closed
@Puru2016

Description

@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:-

Screenshot_22

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

Screenshot_23

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

Metadata

Metadata

Assignees

Labels

Component: ConfigurableProductFixed in 2.4.xThe issue has been fixed in 2.4-develop branchIssue: Clear DescriptionGate 2 Passed. Manual verification of the issue description passedIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentPriority: P2A defect with this priority could have functionality issues which are not to expectations.Progress: doneReported on 2.3.1Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S1Affects critical data or functionality and forces users to employ a workaround.Triage: DoneHas been reviewed and prioritized during Triage with Product Managers

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions