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

Sort by price is not working with custom options as expected in magento 2.3.0 product listing page #22479

Open
dcwnaveen opened this issue Apr 24, 2019 · 22 comments

Comments

@dcwnaveen
Copy link

@dcwnaveen dcwnaveen commented Apr 24, 2019

Sort by price is not working with custom options as expected in Magento 2.3.0 product listing page. Because results are showing based on the product price + lowest customizable option price like product B 130$, product C 140$, and product A 150$ and prices are showing like product B 110$, product C 120$, and product A 100$

Preconditions
Magento 2.3.0 & 2.3-develop
PHP 7.2

Steps to reproduce
Freshly install Magento.
Create 3 products with a custom option. like A product price 100$ customizable option price starts with 50, B product price 110$ customizable option price starts with 20 and C product price 120$ customizable option price starts with 20.

Expected Result
We are expecting sort by price is product A, product B, and product C.(don't need to calculate the customizable option price)
Or
We are expecting the price displays with the lowest customizable option.

Actual result
Its showings like product B, product C, and product A.

@m2-assistant

This comment has been minimized.

Copy link

@m2-assistant m2-assistant bot commented Apr 24, 2019

Hi @dcwnaveen. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@dcwnaveen do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no
@m2-backlog m2-backlog bot added this to Ready for QA in Community Backlog Apr 24, 2019
@krishprakash krishprakash self-assigned this Apr 24, 2019
@m2-assistant

This comment has been minimized.

Copy link

@m2-assistant m2-assistant bot commented Apr 24, 2019

Hi @krishprakash. 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).

    DetailsIf 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.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

@krishprakash

This comment has been minimized.

Copy link

@krishprakash krishprakash commented Apr 24, 2019

@magento-engcom-team give me 2.3-develop instance

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Apr 24, 2019

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

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Apr 24, 2019

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-22479-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@dcwnaveen

This comment has been minimized.

Copy link
Author

@dcwnaveen dcwnaveen commented Apr 24, 2019

@krishprakash

This comment has been minimized.

Copy link

@krishprakash krishprakash commented Apr 24, 2019

@magento-engcom-team give me 2.2-develop instance

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Apr 24, 2019

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

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Apr 24, 2019

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-22479-2-2-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

@dcwnaveen

This comment has been minimized.

Copy link
Author

@dcwnaveen dcwnaveen commented Apr 24, 2019

same issue on 2.2 also

@magento-engcom-team

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Apr 24, 2019

Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99380, MAGETWO-99381 were created

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

@GovindaSharma GovindaSharma self-assigned this Apr 30, 2019
@m2-assistant

This comment has been minimized.

Copy link

@m2-assistant m2-assistant bot commented Apr 30, 2019

Hi @GovindaSharma. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

  • 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 2. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 3. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

@m2-backlog m2-backlog bot moved this from Good First Issue to Dev in Progress in Community Backlog Apr 30, 2019
@GovindaSharma

This comment has been minimized.

Copy link
Member

@GovindaSharma GovindaSharma commented May 4, 2019

#dmcdindia1

@jeovela86 jeovela86 removed their assignment Aug 23, 2019
@m2-backlog m2-backlog bot moved this from Dev in Progress to Good First Issue in Community Backlog Aug 23, 2019
@tiagooctp

This comment has been minimized.

Copy link
Contributor

@tiagooctp tiagooctp commented Sep 14, 2019

#tiagooctp

@miguelfep

This comment has been minimized.

Copy link

@miguelfep miguelfep commented Sep 14, 2019

#MMBR19
@magento I am working on it

@m2-assistant

This comment has been minimized.

Copy link

@m2-assistant m2-assistant bot commented Sep 14, 2019

Hi @miguelfep! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and self-assign the issue.

@miguelfep miguelfep self-assigned this Sep 14, 2019
@m2-assistant

This comment has been minimized.

Copy link

@m2-assistant m2-assistant bot commented Sep 14, 2019

Hi @miguelfep. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

  • 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 2. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 3. If the issue is not relevant or is not reproducible any more, feel free to close it.


@m2-backlog m2-backlog bot moved this from Good First Issue to Dev in Progress in Community Backlog Sep 14, 2019
@miguelfep miguelfep closed this Sep 14, 2019
@m2-backlog m2-backlog bot moved this from Dev in Progress to Done (last 30 days) in Community Backlog Sep 14, 2019
@miguelfep miguelfep reopened this Sep 14, 2019
@m2-backlog m2-backlog bot moved this from Done (last 30 days) to Ready for QA in Community Backlog Sep 14, 2019
@engcom-Charlie engcom-Charlie self-assigned this Sep 16, 2019
@m2-assistant

This comment has been minimized.

Copy link

@m2-assistant m2-assistant bot commented Sep 16, 2019

Hi @engcom-Charlie. 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).

    DetailsIf 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.3-develop branch

    Details- Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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

This comment has been minimized.

Copy link
Contributor

@magento-engcom-team magento-engcom-team commented Sep 16, 2019

Confirmed by @engcom-Charlie
Thank you for verifying the issue. Based on the provided information internal tickets MC-20165 were created

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

@miguelfep miguelfep self-assigned this Sep 16, 2019
@m2-backlog m2-backlog bot moved this from Ready for Dev to Dev in Progress in Community Backlog Sep 16, 2019
@m2-backlog m2-backlog bot moved this from Dev in Progress to Ready for Dev in Community Backlog Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.