Open NetStorm84 opened 4 years ago
Hi @NetStorm84. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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.
@NetStorm84 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
@magento give me 2.4-develop instance
Hi @NetStorm84. Thank you for your request. I'm working on Magento 2.4-develop instance for you
Hi @NetStorm84, here is your Magento instance.
Admin access: https://i-26101-2-4-develop.instances.magento-community.engineering/admin
Login: admin
Password: 123123q
Instance will be terminated in up to 3 hours.
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: :point_down:
[x] 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.
[x] 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.
[x] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[x] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- 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!
[x] 5. Add label Issue: Confirmed
once verification is complete.
[x] 6. Make sure that automatic system confirms that report has been added to the backlog.
:white_check_mark: Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-29961
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.
I can confirm that this indeed happens in the "Wish List" but it happens in the "Shopping Cart" as well.
The Issue still reproducible on the lates 2.4-developer
code
Hi @sdzhepa,
I will resolve the conflict in my open pull request later tonight, this should resolve this issue.
Kind regards, Julian
@Serializator thank you! I have linked this issue with your pr
Based on Triage review, was verified additional case. Can confirm this issue seems to affect only displaying price in Admin If we open the Customer shopping cart = price will be correct(product+option)
4 years this PR has been in progress, might need to look at doing something else.
Hi @engcom-Bravo. 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:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Hi @NetStorm84,
Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the attached video.
Steps to reproduce
https://github.com/magento/magento2/assets/51680745/d07ef849-bc24-42e2-899a-81b1265f9ade
The price shown is the base price of the product and does not include the selection price
Hence Confirming the issue.
Thanks.
Wow this really is low priority. 5 years since I reported the issue 😄
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-11956 is successfully created for this GitHub issue.
:white_check_mark: 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.
:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-11956
:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-11956
There is an issue when creating a backend order, with a product that has Customizable Options. Moving the product to the Wishlist or Cart does not keep the price of the selected options. Although the correct price is shown for the customer in the Frontend, the sidebar shows the incorrect price.
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
The price shown in the left sidebar, should be that of the selected option
Actual result (*)
The price shown is the base price of the product and does not include the selection price
Additional Information
https://github.com/magento/magento2/issues/26101#issuecomment-570705209 https://github.com/magento/magento2/issues/26101#issuecomment-631541616 Update: On Storefront in customers shopping cart price showing correctly (PRD+opt) https://github.com/magento/magento2/issues/26101#issuecomment-632332366