Wrong customer DOB save on backend.

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.51k stars 9.31k forks source link

Wrong customer DOB save on backend. #37894

Open arjunkumar1910 opened 1 year ago

arjunkumar1910 commented 1 year ago

Preconditions and environment

Magento version
Anything else that would help a developer reproduce the bug

Steps to reproduce

Login to the Magento246 backend.
Go to the customer menu and click on the All Customer submenu.
Click on Add New Customer and Fill all customer details.
Add future dob in the text box.
Save the customer and customer saved successfully.
In the customer grid future date is showing, but in the edit form current date showing.

check following video for details

https://www.awesomescreenshot.com/video/20036011?key=d479fef608118b0dc1bda5ca8e0fe0e3

Expected result

The customer should not be saved in the grid and the date should be current if a future date is selected.

Actual result

The future date is shown in the grid.

Additional information

No response

Release note

No response

Triage and priority

[X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[X] 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.
[X] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[X] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 1 year ago

Hi @arjunkumar1910. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release
For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.

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

m2-assistant[bot] commented 1 year 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).
[ ] 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
- 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.

engcom-Bravo commented 1 year ago

Hi @arjunkumar1910,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to reproduce

Go to the customer menu and click on the All Customer submenu.
Click on Add New Customer and Fill all customer details.
Add future dob in the text box.
Save the customer and customer saved successfully.
In the customer grid future date is showing, but in the edit form current date showing.

We have created a customer with DOB 18-AUG-2023.(future date).it is showing in admin grid as as 18-AUG-2023

While Customer>>Account Information still it is showing as 17-AUG-2023.

It should be 18-AUG-2023 or it should give error while creating customer accounts with future dates.

Hence Confirming the issue.

Thanks.

github-jira-sync-bot commented 1 year ago

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

m2-assistant[bot] commented 1 year ago

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

pabodah commented 1 year ago

I tested this in a default Magento 2.4.6 instance. Seems like the DOB cannot be set as a future date via the datepicker and also by editing manually. If you try to do so, a notification will be displayed under the field and the customer cannot be saved which seems to be the correct approach.

Paboda Hettiarachchi - Customers - Customers - Magento Admin 2023-09-21 11-39-24