Fix upgrade on participant_register date #14427
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
On testing I found the conversion routing on participant register date wasn't working properly when
upgrading to 5.15 - this fixes
Before
Jcalendar groups are stored with hard-date formatted fields in participant_register_date_low & high and then a relative format in the relative dates array
After
For relative dates relative_dates array & the high & low fields should be empty. participant_register_date_relative should be handled
Technical Details
@seamuslee001 can you take a look at this - it could be a potentially regression about to hit 5.15 if not resolved before it's cut but my brain has stopped processing it. I have lot of groups & they have names which meant something once but now I can't figure out whether old new smartgroup should be the same as 'a bit newer group' or more like 'old group but not as old as old group'
Comments
@mattwire I think you merged the upgrade but I guess neither of us tested well