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

error Customer reorder with unupdated product prices (?) #30663

Closed
1 of 5 tasks
JMLucas96 opened this issue Oct 27, 2020 · 4 comments
Closed
1 of 5 tasks

error Customer reorder with unupdated product prices (?) #30663

JMLucas96 opened this issue Oct 27, 2020 · 4 comments
Assignees
Labels
not-confirmed Use for Issue that was closed during confirmation Reported on 2.1.x Indicates original Magento version for the Issue report.

Comments

@JMLucas96
Copy link

JMLucas96 commented Oct 27, 2020

When a customer reorders old order, Magento allows it but with old product prices. Reorder would have to updated prices.

Preconditions (*)

  1. Magento 2.1.8

Steps to reproduce (*)

  1. Buy one product on magento with customer account.
  2. Change product price on admin.
  3. Reorder previous order
    image

Expected result (*)

  1. Magento allows reorder with the updated product prices.

Actual result (*)

  1. Magento allows reorder but with the old product prices.

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

  • 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
Copy link

m2-assistant bot commented Oct 27, 2020

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

@m2-assistant
Copy link

m2-assistant bot commented Oct 27, 2020

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

Sorry, something went wrong.

@engcom-Delta
Copy link
Contributor

Hi @JMLucas96 thank you for your report, I'm not able to reproduce issue by steps you described on clean 2.4-develop
Manual testing scenario:

  • Create simple product with Price=100
  • Place order with simple product by registered customer
  • Change simple product price to 50$
  • Go to My Account->My Orders page
  • Click Reorder

Result:
✔️ Order is placed with new product price
Peek 2020-10-27 22-00

If you'd like to update the issue, please reopen it.

@engcom-Delta engcom-Delta added the not-confirmed Use for Issue that was closed during confirmation label Oct 27, 2020
@JMLucas96
Copy link
Author

Hi @engcom-Delta thank you to test in Magento 2.4 fresh install, but issue is in magento 2.1.8 and is it possible that I need to update controller with Magento 2.4 version... Can you tell me what file manage reorder functionality?

@sdzhepa sdzhepa added the Reported on 2.1.x Indicates original Magento version for the Issue report. label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-confirmed Use for Issue that was closed during confirmation Reported on 2.1.x Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

3 participants