Details
-
Type: Bug
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.7.21
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
-
Verified?:No
Description
You can replicate this bug in dmaster doing the following:
- Create a custom group in Contact and include one custom data type
- Edit a contact and set a date in this custom field. Important to set a date 4 or 5 years ago. For example: 01/01/2010
- Edit the custom field and set "Dates may be up to 1 years prior to current date".
- Go again to the contact and check the date. It has changed to 01/01/2016
I attach an image where you can see that the value of the custom field is correct (2010-07-22 in the img) but instead shows 01/01/2016.
That's caused by the option of the "Dates may be...".
It shouldn't change the dates already set, only the new ones.