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

Partial dates assigning current date portions to the missing sections #481

Closed
tlammer opened this issue Oct 29, 2018 · 3 comments
Closed
Labels
1 - Bug Incorrect behavior of the product impact:many res:fixed (deprecated) Problem has been fixed
Milestone

Comments

@tlammer
Copy link

tlammer commented Oct 29, 2018

partial date fields are assigning random values to the missing portions of the dates.
Reported by South Africa
Confirmed in db1 of the test server
I changed the format to both month/year and just year in the start date and cataloged date, entered a value (02/1915 or 1915), and saved the record. When I viewed the date in the full date format, values like 10 and 28 were put in the missing sections.

@tlammer tlammer added the 1 - Bug Incorrect behavior of the product label Oct 29, 2018
@tlammer
Copy link
Author

tlammer commented Mar 27, 2019

The values are not random. The missing date portions are being filled in by the values for the date the record is created

@tlammer tlammer changed the title Partial dates assigning random numbers to the missing sections Partial dates assigning current date portions to the missing sections Apr 16, 2019
@tlammer tlammer added this to the next-release milestone Apr 16, 2019
@benanhalt benanhalt added the res:fixed (deprecated) Problem has been fixed label Apr 19, 2019
@yvonneekanim
Copy link

Partial dates are still assigning current date to missing day/month

@benanhalt benanhalt removed the res:fixed (deprecated) Problem has been fixed label Apr 25, 2019
@benanhalt
Copy link
Contributor

@yvonneekanim when I was fixing the test server I think I mixed up the master and development branches. Would you mind checking this again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Bug Incorrect behavior of the product impact:many res:fixed (deprecated) Problem has been fixed
Projects
None yet
Development

No branches or pull requests

3 participants