Sorting of configurable products on category pages is affected by the child product data

[hewgim]

Preconditions and environment

Magento vanilla version 2.4.5 and 2.4.6 with sample data
Elastic Search 7

Steps to reproduce

Create a new sort attribute called Custom Sort Order with drop down values 1,2,3,4,5

Add the Custom Sort Order attribute to the 'Top' attribute set

Set the Custom Sort order to 3 for all Tops

For the Juno Jacket configurable product set the custom sort order to 5

For the Juno Jacket child products set the custom sort order to 2

Goto to Women->Tops->Jackets and sort by Custom Sort Order

Expected result

The Juno Jacket configurable product should display last in the Jackets category because it has the highest sort order

Actual result

The Juno Jacket does not display last.

However if you now set all the Juno Jacket children with a sort priority of 5, the Juno Jacket configurable product will display last.

That means that the sorting of a parent configurable product is dependent on the sort data of both the parent and its children which doesn't make sense and is rather confusing. This appears to be behaviour brought in by the use of Elastic Search rather than MySql

Additional information

It is interesting to note that when you reverse the direction of the sort the Juno Jacket does appear first as expected.

I ran this in a debugger and stopped in vendor/magento/module_elastic_search-7/SearchAdapter/Adapter.php which appears to be used to obtain the sorted list of products. When I look at the $rawResponse array I can see that the sort data for the Juno Jacket configurable product contains the Custom Sort Order data from the children. When the direction of sorting is reversed the sort data contains the Custom Sort Order data from the parent.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @hewgim. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.

[engcom-Bravo]

Hi @hewgim,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Create a new sort attribute called Custom Sort Order with drop down values 1,2,3,4,5
• Add the Custom Sort Order attribute to the 'Top' attribute set
• Set the Custom Sort order to 3 for all Tops
• For the Juno Jacket configurable product set the custom sort order to 5
• Goto to Women->Tops->Jackets and sort by Custom Sort Order

Juno Jacket Configurable product displaying last in the jackets category.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[hewgim]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @hewgim. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @hewgim, here is your Magento Instance: https://3639c42b336a0e3ce5ccb53ccde1073a.instances-prod.magento-community.engineering
Admin access: https://3639c42b336a0e3ce5ccb53ccde1073a.instances-prod.magento-community.engineering/admin_edfe
Login: 70253529
Password: 8a8853934e95

[hewgim]

Hi @engcom-Bravo

Apologies but I missed a crucial step in the steps to reproduce.

For the Juno Jacket child products set the custom sort order to 2

I've amended the Steps To Reproduce above.

After I do this the Juno jacket appears first when it should appear last

[m2-assistant]

Hi @engcom-November. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.