Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Product Merchandising Display order as REST API sorting option #29254

Open
thisfiore opened this issue Jul 24, 2020 · 7 comments
Open

Product Merchandising Display order as REST API sorting option #29254

thisfiore opened this issue Jul 24, 2020 · 7 comments
Labels
feature request Issue: ready for confirmation Priority: P3 May be fixed according to the position in the backlog. Progress: ready for grooming Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. stale issue

Comments

@thisfiore
Copy link

Description (*)

Have the product merchandising order accessible using REST api search calls.
At the moment look we cannot access the sorting set using this UI

Screenshot 2020-07-24 at 11 03 14

Can't find any documentation about it, or can you confirm this is not possible at the moment?

@m2-assistant
Copy link

m2-assistant bot commented Jul 24, 2020

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

Please, add a comment to assign the issue: @magento I am working on this


⚠️ 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Jul 24, 2020
@ghost ghost added this to Ready for QA in Community Backlog Jul 24, 2020
@sidolov sidolov added this to Ready for Grooming in Low Priority Backlog Sep 24, 2020
@sidolov sidolov added this to Ready for Confirmation in Issue Confirmation and Triage Board Oct 21, 2020
@ghost ghost removed this from Ready for QA in Community Backlog Oct 21, 2020
@ghost ghost removed this from Ready for Grooming in Low Priority Backlog Oct 21, 2020
@ghost ghost added Issue: ready for confirmation and removed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Oct 21, 2020
@sivaschenko
Copy link
Member

@thisfiore thanks for the feature request! Can you please add more information to the description to make it a bit more clear?

@sivaschenko sivaschenko added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Nov 6, 2020
@m2-community-project m2-community-project bot added this to Ready for Grooming in Feature Requests Backlog Nov 6, 2020
@m2-community-project m2-community-project bot removed this from Ready for Confirmation in Issue Confirmation and Triage Board Nov 6, 2020
@stale
Copy link

stale bot commented Jan 21, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

@stale stale bot added the stale issue label Jan 21, 2021
@thisfiore
Copy link
Author

Just to clarify:
In the current release, it's not possible to access ordered products data using REST API Seach calls.
Would be interesting to enable REST API to access correct ordering if is set up from the CMS, giving a parameter on current search call or different END POINT for REST API with VISUAL MERCHANDISING ORDERING

@stale stale bot removed the stale issue label Jan 27, 2021
@stale
Copy link

stale bot commented Apr 14, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

@stale stale bot added the stale issue label Apr 14, 2021
@dverkade
Copy link
Member

Posting a comment. Issues should not be automatically closed.

@stale stale bot removed the stale issue label Apr 18, 2021
@stale
Copy link

stale bot commented Sep 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 28 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

@stale stale bot added the stale issue label Sep 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issue: ready for confirmation Priority: P3 May be fixed according to the position in the backlog. Progress: ready for grooming Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. stale issue
Projects
Feature Requests Backlog
  
Ready for Grooming
Development

No branches or pull requests

4 participants