Converting an all-day RECURRING event to time-based screws it up (becomes a 3-days-long time-based event)
In version 43.1, we have a variant of #233 (closed) / #168 (closed) resurfacing, that I have encountered when trying to test #178.
How to reproduce:
- Create an "All day" weekly recurring event, save the event. This is important! Do NOT create it as a time-based event from the start.
- Edit the event again, and convert it from an all-day event to a time-based event, by setting its start time to 10:00 and letting (or setting) the end time to 11:00 AM. Take note that the start date and end date are still the same, there is no indication that the end date was changed...
- Save the changes, and ask to apply them to All events (or subsequent events)
Result:
Instead of a single-day time-based one-hour-long event recurring the same day each week, it becomes a 3-days long event recurring each week. Even if you were extra careful and forcefully set the end date to match the start date, the backend ignores what the GUI had set, the end date will never respect what you have put in the field!
Maybe related to #705 (closed), #774 (closed), #724, and the long-standing #91 (closed) / #45 (closed)...