Closed
Bug 401686
Opened 17 years ago
Closed 12 years ago
Impossible to restore exception (exdate) after deleting it
Categories
(Calendar :: General, defect)
Calendar
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 378443
People
(Reporter: omar.bajraszewski, Unassigned)
Details
I couldn't find any similar bug.When I create a repeating event and then delete occurrences and after that update the event, the deleted events do not appear 1)Create one hour event repeating daily (5 appointments) 2)Delete first three occurrences 3)Edit the event and change title and hours of the event Actual result: I can't see the event for first three days Expected result: If I update all occurrences the status of the event should be reset and the deleted events should reappear. So In this case I should see 5 updated occurrences, not only 2.
Comment 1•17 years ago
|
||
I disagree. If I delete occurrences from a repeating event they should not reappear but stay deleted.
Reporter | ||
Comment 2•17 years ago
|
||
Imagine a situation: there is a meeting everyday at 6 pm. On every Monday and every Tuesday at 6 pm you're busy and can't attend it. So you delete the event for Monday and Tuesday. Then the meeting time is changed to 8pm. At 8 pm you're free and can attend the meeting. You edit the event but the event doesn't display for Monday and Tuesday. In my opinion it's not alright. If you only change a title it's alright but in some cases the deleted occurrences should be restored.
Comment 3•14 years ago
|
||
I guess we just misunderstood. Its true that its impossible to restore exdates. Possibly, this could be marked as a duplicate of bug 378443. I can imagine no way to integrate this into the views, but it could possibly be integrated into the event dialog.
OS: Windows XP → All
Hardware: x86 → All
Summary: When exceptions are created it's impossible to update the event → Impossible to restore exception (exdate) after deleting it
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•