magento2 icon indicating copy to clipboard operation
magento2 copied to clipboard

Duplicate shipping address in Checkout shipping - magento2

Open sanganb opened this issue 4 years ago • 17 comments

Preconditions (*)

1.Magento 2.3.5 2. Magento 2.4-develop

Steps to reproduce (*)

  1. GO to checkout as logged in user
  2. Its shows already saved shipping address (OR add shipping address in customer my account)
  3. Click Add new Address button
  4. Add address same as already exists in site
  5. which is allowed to create new address

Expected result (*)

  1. When we save new address in checkout shipping form same as existing address which should select existing address
  2. After order it should not create new address

Actual result (*)

  1. [Screenshots, logs or description image ]

image

image

Summary

When we add existing address as new address in checkout shipping form its should select existing address and ship to that address rather than creating new address each time

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”.

sanganb avatar Feb 26 '21 06:02 sanganb

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


:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

m2-assistant[bot] avatar Feb 26 '21 06:02 m2-assistant[bot]

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).

    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.

m2-assistant[bot] avatar Feb 26 '21 14:02 m2-assistant[bot]

:white_check_mark: Confirmed by @engcom-Bravo Thank you for verifying the issue. Based on the provided information internal tickets MC-41083 were created

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.

magento-engcom-team avatar Feb 26 '21 14:02 magento-engcom-team

@magento I am working on this

vlmed avatar Mar 23 '21 15:03 vlmed

Hi @vlmed ,

Was you able to fix this issue? If you can please provide a patch or something we can refer to in the meantime please.

Thanks, Anup

anupwankhede avatar May 14 '21 12:05 anupwankhede

Is there any update on the progress of this please?

brucemead avatar Jun 01 '21 08:06 brucemead

Can we get some progress report on this, please?

mamsincl avatar Jun 11 '21 15:06 mamsincl

Fallowing on that issue , expecting a release of a patch to fix this adress duplication I am suprised that this is considered as low priority

coutes avatar Dec 10 '21 16:12 coutes

@magento I am working on this

Any fallow up with MC-41083

coutes avatar Dec 10 '21 16:12 coutes

Hi @coutes! :wave: Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

m2-assistant[bot] avatar Dec 10 '21 16:12 m2-assistant[bot]

Hi @sanganb,

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 screenshots.

Screenshot 2024-07-12 at 13 03 54

After placing an order it is creating duplicates with the same address.

Hence Confirming the issue.

Thanks.

engcom-Bravo avatar Jul 12 '24 07:07 engcom-Bravo

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12463 is successfully created for this GitHub issue.

github-jira-sync-bot avatar Jul 12 '24 08:07 github-jira-sync-bot

: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.

m2-assistant[bot] avatar Jul 12 '24 08:07 m2-assistant[bot]

Hi, any solution to this yet? It's still happening in 2.4.6-p8.

davidpixie avatar Jan 24 '25 10:01 davidpixie

Hi @davidpixie ,

Our internal team is currently working on this. We will keep providing the updates here as progress is made.

Thank you for your patience!

engcom-November avatar Jun 17 '25 13:06 engcom-November

Hi @sanganb,

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 screenshots.

Image

After placing an order it is creating duplicates with the same address.

Hence Confirming the issue.

Thanks.

engcom-November avatar Jun 17 '25 13:06 engcom-November

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-12463

github-jira-sync-bot avatar Jun 17 '25 13:06 github-jira-sync-bot