1145905 - Event creation deletes last day if repeated

Status: RESOLVED DUPLICATE of bug 566149

(Calendar :: Lightning Only, defect)

Description

[Chris Newby]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150305021524

Steps to reproduce:

Created an event that repeats for 3 days


Actual results:

If I create an event on the 21st of a month and then select for it to repeat until the 23rd when you save the event it is only from the 21st to the 22nd, you can then go back into the event and change it to the 23rd and all is OK.


Expected results:

When selecting the event to repeat for three days it should repeat for three days

Comment 1

[Decathlon]

Hi Chris,
could you please verify if steps to reproduce are the same of bug 566149?
In particular, do you change the End Date/time to an earlier value than that one proposed in the datepicker *before* changing the Until Date?

Comment 2

[Chris Newby]

Hi,

Yes it would appear that this is a dupe of that but, in the instance where I came across it I was doing a series of 3 day entries (the F1 race calendar) so the procedure was the same for each of the events.

1. Enter event name
2. Change the calendar from home to another
3. Change the time (which was a time earlier that the current time of day)
4. Set up the repeat (daily, repeats for three days Friday - Sunday)
5. Set the reminder
6. Save and close.

After reading the previous bug report I can report that if I choose a time later than the current time the entry is created correctly also if I choose the repeat before changing the time (to a time earlier than the current time) the entry is created correctly.

One thing I noted in the other bug report was that when the event was edited that the end date was correct, in my case this is not the fact when I go to edit the event the repeat date is a day short of what was entered.

Hope this is of use to you.

Comment 3

[Decathlon]

I have to correct my comment #1, where I wrote "End date/time" I had to write "Start date/time", anyway, from your steps to reproduce, I think it is exactly bug 566149 so I mark this as duplicate.