[GraphQL] related, upsell and crosssell products query ignoring the position they were saved in

[MarianNapi]

Preconditions and environment

• Magento version 2.4.5

Steps to reproduce

1. Create a product
2. add other products as related, upsell or crosssell products and sort them in a random order
3. Request these fields via the GraphQl API

Expected result

The related, upsell and crosssell products should be returned in the specific order they were saved in.

Actual result

The related, upsell and crosssell products are returned sorted by their actual product entity_id.

Additional information

No response

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 @MarianNapi. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[MarianNapi]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[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-deployment-service]

Hi @MarianNapi, here is your Magento Instance: https://ca36ac9d51d32a8de5e3307596911ff3.instances.magento-community.engineering
Admin access: https://ca36ac9d51d32a8de5e3307596911ff3.instances.magento-community.engineering/admin_f93e
Login: 3140e3e9
Password: 748006e24d05

[MarianNapi]

I can reproduce the issue on a vanilla magento instance with version 2.4-develop

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://ca36ac9d51d32a8de5e3307596911ff3.instances.magento-community.engineering
Admin access: https://ca36ac9d51d32a8de5e3307596911ff3.instances.magento-community.engineering/admin_0715
Login: cecae9b7
Password: 67f934994ee3

[engcom-Bravo]

Hi @MarianNapi,

Thank you for reporting and collaboration.

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

Steps to reproduce
1.Create a product
2.add other products as related, upsell or crosssell products and sort them in a random order
3.Request these fields via the GraphQl API

The related, upsell and crosssell products are returned sorted by their actual product entity_id.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-7014 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
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.

[engcom-Hotel]

@engcom-Bravo We need to check this functionality in the frontend as well. So please reverify it and let us know the outcome here.

[engcom-November]

Hi @MarianNapi ,
Development team is currently working on this issue.
Thank you.

[engcom-Bravo]

Hi @MarianNapi,

Verified the issue on Magento 2.4-develop instance and the issue is no longer reproducible.Hence we are closing this issue.

Thanks.

[MarianNapi]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @MarianNapi, here is your Magento Instance: https://ca36ac9d51d32a8de5e3307596911ff3.instances-prod.magento-community.engineering
Admin access: https://ca36ac9d51d32a8de5e3307596911ff3.instances-prod.magento-community.engineering/admin_e846
Login: 5027b511
Password: c2e3dd4bb285

[Xeo67]

Is there a fix ? I have the same issue on Magento 2.4.5-p4

There is no sorting on position attribute when Magento search the relation in vendor/magento/module-related-product-graph-ql/Model/DataProvider/RelatedProductDataProvider.php