while doing checkout by multiple address, at order review page for first address it only display the charges as same of second address but calculation is correct

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

http://www.magento.com

Open Software License 3.0

11.5k stars 9.31k forks source link

while doing checkout by multiple address, at order review page for first address it only display the charges as same of second address but calculation is correct #24895

Closed Khushbu-Webkul-QA closed 4 years ago

Khushbu-Webkul-QA commented 5 years ago

Preconditions (*)

magento version: 2.3.3

Steps to reproduce (*)

start checkout at multiple address, e.g two different address
select different-2 shipping methods for both the address, e.g for first address-select flat rate(10$) and table rate(20) for another address
at review order page, it displaying the second shipping rate charges at first address also
but calculation is correct

Expected result (*)

It should display the correct shipping charges of first address

Actual result (*)

for first address it display the second address shipping charges

order review page- Screenshot (5)

m2-assistant[bot] commented 5 years ago

Hi @Khushbu-Webkul-QA. 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.3-develop instance - upcoming 2.3.x release

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

@Khushbu-Webkul-QA do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

[ ] yes
[ ] no

Join Magento Community Engineering Slack and ask your questions in #github channel.

m2-assistant[bot] commented 5 years ago

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

[ ] 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.
[ ] 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.

Khushbu-Webkul-QA commented 5 years ago

yes i can reproduce this issue.

engcom-Bravo commented 5 years ago

Hello @Khushbu-Webkul-QA. Thanks for reporting. It seems such an issue was really present in 2.2-develop branch which is already closed now. But it probably has been fixed in 2.3-develop as we are not able to currently reproduce it on that version. Could You please confirm You can reproduce it on the very 2.3-develop version as You are asked in the comment above. Thank You.

Khushbu-Webkul-QA commented 5 years ago

Hello, The issue is also present in magento 2.3.2 Kindly check the screen shots

Screenshot (9) Screenshot (10) Screenshot (11) Screenshot (12)

Khushbu-Webkul-QA commented 5 years ago

Please find the attached video magento_multishipping_2.3.x.mov.zip

cdbessig commented 5 years ago

We have also found this bug on Friday / Today and are fighting with it too.

cdbessig commented 5 years ago

@magento give me 2.3-develop instance

magento-engcom-team commented 5 years ago

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

magento-engcom-team commented 5 years ago

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

cdbessig commented 5 years ago

@magento-engcom-team the url does not work. The url resolves to an ip, but the ip address does not answer or connect or ping.

engcom-Bravo commented 5 years ago

Yes @Khushbu-Webkul-QA, @cdbessig it is 100% reproducible on 2.3.2 too, I've just tried. It is only 2.3-develop, that I can not reproduce the issue on. So please try to reproduce it on 2.3-develop. (The links above, by the way, are already usable.) Thank You.

Khushbu-Webkul-QA commented 5 years ago

I am proceeding to checkout but at select shipping method page, table rate shipping method not display but enable from admin end, check screen shots

Screenshot (15) Screenshot (16)

engcom-Bravo commented 5 years ago

@Khushbu-Webkul-QA, do You mean there's no field displayed in admin where You can enter a csv file with rates for Table Rates shipping method?

m2-assistant[bot] commented 5 years ago

Hi @deepakk-webkul. 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:

[ ] 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.
[ ] 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!

Join Magento Community Engineering Slack and ask your questions in #github channel.

deepakk-webkul commented 5 years ago

@magento give me 2.3-develop instance

magento-engcom-team commented 5 years ago

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

magento-engcom-team commented 5 years ago

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

deepakk-webkul commented 5 years ago

Hello @Khushbu-Webkul-QA I can't reproduce this issue on fresh Magento 2.3-develop. It's working fine.

2019-10-09-12-45-i-24895-2-3-develop instances magento-community engineering

So i have to close it. Thanks for your report!

Khushbu-Webkul-QA commented 4 years ago

magento version: 2.3.3
mode: production
php version: 7.2
varnish: enable
js,css,html: merged and minified

Issue was not reproduce on develop but found on magento version 2.3.3

Screenshot (41)

Screenshot (42)

mahesh-rajawat commented 4 years ago

@deepakk-webkul this issue still exists in 2.3.3.

m2-assistant[bot] commented 4 years ago

Hi @webkul-ratnesh. 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:

[ ] 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.
[ ] 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!

Join Magento Community Engineering Slack and ask your questions in #github channel.

Khushbu-Webkul-QA commented 4 years ago

@magento give me 2.3-develop instance

magento-engcom-team commented 4 years ago

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

magento-engcom-team commented 4 years ago

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

engcom-Charlie commented 4 years ago

Hello, everyone! This issue should be closed as not reproducible.