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.

Sign up for GitHub

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

Jump to bottom

Magento 2.4.1 - ZIP code doesn't change unless other field is edited #30951

Closed
4 tasks
gondas33 opened this issue Nov 17, 2020 · 13 comments · May be fixed by #32290
Closed
4 tasks

Magento 2.4.1 - ZIP code doesn't change unless other field is edited #30951

gondas33 opened this issue Nov 17, 2020 · 13 comments · May be fixed by #32290
Assignees
@nabhanmaswood98
Labels
Component: CustomerAttributes Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: ready for confirmation Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.4.1 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.

Comments

@gondas33
Copy link

gondas33 commented Nov 17, 2020 •
edited by engcom-Alfa
Loading

Preconditions (*)

  1. Magento 2.4-develop
  2. Magento 2.4.1

Steps to reproduce (*)

  1. Create an order where the zip code contains the ('.') character at the end;

2020-11-19_12-17
2. Click on the Edit billing address button;
3. Remove the ('.') character from the zipcode;
2. Save

Expected result (*)

  1. New ZIP code should save without the symbol at the end

Actual result (*)

  1. ZIP code doesn't change unless another field is edited(like address) or the whole zipcode is changed
    Peek 2020-11-19 12-20

Issue was also mentioned on: https://magento.stackexchange.com/questions/257750/magento-2-cant-change-the-zip-code-in-order

Reproduced on dev: https://www.loom.com/share/fad8304feab342c6b560155488dae1a7

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.
  • [ X] 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”.
@m2-assistant
Copy link

m2-assistant bot commented Nov 17, 2020

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

⚠️ 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

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

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

@gondas33
Copy link
Author

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @an4rei. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

Hi @an4rei, here is your Magento Instance: https://a54429fd7f6e275b2993069b6c83a276-2-4-develop.instances.magento-community.engineering
Admin access: https://a54429fd7f6e275b2993069b6c83a276-2-4-develop.instances.magento-community.engineering/admin_247b
Login: 12e12af9
Password: b3da8fded526

@gondas33
Copy link
Author

issue is reproducible on dev: https://www.loom.com/share/fad8304feab342c6b560155488dae1a7
note: the zipcode must contain a '.' at the end, it might be the same case for other symbols as well.

@engcom-Alfa engcom-Alfa self-assigned this Nov 18, 2020
@m2-assistant
Copy link

m2-assistant bot commented Nov 18, 2020

Hi @engcom-Alfa. 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).

    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.

Sorry, something went wrong.

@engcom-Alfa engcom-Alfa added Reported on 2.4.1 Indicates original Magento version for the Issue report. Component: CustomerAttributes Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Nov 19, 2020
@engcom-Alfa engcom-Alfa added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch and removed Progress: dev in progress labels Nov 19, 2020
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-39186 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@stale
Copy link

stale bot commented Feb 3, 2021

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!

@stale stale bot added the stale issue label Feb 3, 2021
@gondas33
Copy link
Author

gondas33 commented Feb 3, 2021

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!

issue is still relevant

@stale stale bot removed the stale issue label Feb 3, 2021
@nabhanmaswood98
Copy link

@magento add to contributors team

@m2-assistant
Copy link

m2-assistant bot commented Feb 18, 2021

Hi @nabhanmaswood98! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

@nabhanmaswood98
Copy link

@magento I am working on it

@nabhanmaswood98 nabhanmaswood98 mentioned this issue Feb 25, 2021
Open
4 tasks
@engcom-Bravo
Copy link
Contributor

Hi @gondas33,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the attached video.

Screen.Recording.2024-06-05.at.10.00.54.mov

New ZIP code should save without the symbol at the end

Hence We are closing this issue.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nabhanmaswood98 nabhanmaswood98

Labels
Component: CustomerAttributes Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: ready for confirmation Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.4.1 Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

MC-39186: ZIP code doesn't change unless other field is edited nabhanmaswood98/magento2
5 participants
@gondas33 @magento-engcom-team @engcom-Alfa @engcom-Bravo @nabhanmaswood98