Open Bug 554545 Opened 15 years ago Updated 2 years ago

Recurring event has wrong end date after save/close

Categories

(Calendar :: Dialogs, defect)

Lightning 1.0b1
x86_64
Windows Vista
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: ochoviii, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3 ThunderBrowse/3.2.8.1 I set up the recurrence for a weekly event lasting several months, making sure to set the correct end date (ie 4/27/2010). When I hit save and close, the end date is changed to end at the sixth occurrence or so. (ie start: 1/19/10, end: 2/23/10; start: 1/23/10, end: 3/2/10). When I go back and change it again to the correct date, it holds. Reproducible: Always Steps to Reproduce: 1.create an event in the calendar (ie a weekly class) 2.set up a weekly recurrence lasting several months (ie a semester-start in Jan, end in late Apr) 3.save and close, then open even and look at actual end date. Actual Results: The end date occurs after about six occurrences Expected Results: It should have kept the event recurring to the original end date. none that I'm aware of
Do you mean the end date of the single occurrence or do you mean the until date of the entire recurrence rule? If you enter the date value via keyboard ensure that you press Tab key to move focus away from input field. Otherwise you'll experience Bug 392448.
Version: unspecified → Lightning 1.0b1
I mean the end date of the entire recurrence rule. I don't use the keyboard, I use the drop down menu. I tried it again using a Tab after selecting the end date and got the same result--the recurrence ended at the 6th occurrence. I looked at Bug 392448, and it is a similar problem but not the same. I did do a bug check before reporting this. Thanks!
Component: Lightning Only → General
Component: General → Dialogs
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.