Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.7.16
-
Fix Version/s: 4.7.18
-
Component/s: None
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
-
Verified?:No
Description
This is follow on from CRM-19140 & it extends the change to custom dates to the membership fields. Still outstanding are the contribution date fields - which are reflected in this issue
It feels safer to tackle these membership date fields first & to finish the conversion rather than having profile date fields remain inconsistent.
I have been able to test this on the 'update multiple memberships' and 'batch data entry' screens. In the case of the latter the membership date fields seemed really confusing as they did not load existing defaults & I believe the intent is to leave them blank to be calculated.