Closed navarr closed 5 months ago
Hi @navarr. 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-engcom-team give me {$VERSION} instance
where {$VERSION}
is version tags (starting from 2.2.0+) or develop branches (2.2-develop +).
For more details, please, review the Magento Contributor Assistant documentation.
@navarr do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
@magento-engcom-team give me 2.2-develop instance
Hi @navarr. Thank you for your request. I'm working on Magento 2.2-develop instance for you
Hi @navarr, here is your Magento instance.
Admin access: https://i-17425-2-2-develop.engcom.dev.magento.com/admin
Login: admin
Password: 123123q
Instance will be terminated in up to 3 hours.
@navarr , thank you for your report. We've acknowledged the issue and added to our backlog.
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!
@magento-engcom-team give me 2.4-develop instance
Hi @navarr. Thank you for your request. I'm working on Magento instance for you.
Hi @navarr, here is your Magento Instance: https://5161c12f2cbe4c20a233551fe0791c52-2-4-develop.instances.magento-community.engineering Admin access: https://5161c12f2cbe4c20a233551fe0791c52-2-4-develop.instances.magento-community.engineering/admin_d12c Login: d101717e Password: 823615cb0514
I've updated the issue with slightly different recreation steps for 2.4; as the original issue was fixed
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!
There hasn't been a non-patch release since the last time I confirmed this issue. I don't believe it's qualified to be stale yet
@magento I'm working on it
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
.@magento give me 2.4-develop instance
Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.
Hi @engcom-Bravo, here is your Magento Instance: https://a580233b9d08ea9c20797b8817307472.instances-prod.magento-community.engineering Admin access: https://a580233b9d08ea9c20797b8817307472.instances-prod.magento-community.engineering/admin_152d Login: 03c8e4c0 Password: cbf0bacc4d06
Hi @navarr,
Thanks for your reporting and collaboration.
We have verified the issue in Latest 2.4-develop instance and the issue is no more reproducible.Hence We are closing this issue.
Steps to reproduce
@engcom-Bravo doesn't that screenshot show that you recreated the issue? If the tax rates are still the same, it's showing new York tax for a California address
The expected result is 83c of tax, but you've got 84
Under certain scenarios the tax displayed in checkout for a virtual product does not match the address selected by the billing method
Preconditions
2.3-develop
-- Updated(02/15/2021): Modified for similar issue on2.4-develop
Steps to reproduce
Video Recreation
Expected result
Actual result
Notice