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

Deleted customer address not removed from existing quotes #39562

Open
1 of 5 tasks
JamesFX2 opened this issue Jan 21, 2025 · 3 comments
Open
1 of 5 tasks

Deleted customer address not removed from existing quotes #39562

JamesFX2 opened this issue Jan 21, 2025 · 3 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7-p2 Indicates original Magento version for the Issue report.

Comments

@JamesFX2
Copy link

Preconditions and environment

  • Magento version 2.4.7-p2
  • Anything else that would help a developer reproduce the bug

Steps to reproduce

  1. Create a customer account with multiple addresses.
  2. Go to checkout, set the billing and shipping address to one of them.
  3. In a new tab, delete this address via the customer account area.
  4. Return to the checkout. This address is still in place.

Expected result

When customer address is removed, any quote_address lines with this as the FK (customer_address_id) are removed.

Actual result

Deleted address is retained in quote_address.

Additional information

No response

Release note

No response

Triage and priority

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

m2-assistant bot commented Jan 21, 2025

Hi @JamesFX2. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ 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, join the Community Contributions Triage session to discuss the appropriate ticket.

@engcom-Bravo engcom-Bravo self-assigned this Jan 22, 2025
Copy link

m2-assistant bot commented Jan 22, 2025

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

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- 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.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.7-p2 Indicates original Magento version for the Issue report. label Jan 22, 2025
@engcom-Bravo
Copy link
Contributor

Hi @JamesFX2,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are not able to reproduce the issue.Kindly refer the attached video.

Screen.Recording.2025-01-22.at.10.49.38.am.mov

The Customer address was removed in the checkout.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Jan 22, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Jan 22, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Jan 22, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Jan 23, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Jan 23, 2025
@magento-ct-gh-projects-svc magento-ct-gh-projects-svc moved this from Needs Update to Ready for Confirmation in Issue Confirmation and Triage Board Jan 23, 2025
@magento-ct-gh-projects-svc magento-ct-gh-projects-svc added Issue: ready for confirmation and removed Issue: needs update Additional information is require, waiting for response labels Jan 23, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Jan 23, 2025
@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Jan 23, 2025
@magento-ct-gh-projects-svc magento-ct-gh-projects-svc added Issue: needs update Additional information is require, waiting for response and removed Issue: ready for confirmation Issue: needs update Additional information is require, waiting for response labels Jan 23, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Jan 23, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.7-p2 Indicates original Magento version for the Issue report.
Projects
Development

No branches or pull requests

3 participants