Bug 493234 - Rescheduling a reoccurring event in month or week view does not update the event in day view
Summary: Rescheduling a reoccurring event in month or week view does not update the ev...
Status: REPORTED
Alias: None
Product: korganizer
Classification: Applications
Component: general (other bugs)
Version First Reported In: 6.2.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-17 00:53 UTC by Tom
Modified: 2024-09-17 00:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom 2024-09-17 00:53:13 UTC
SUMMARY
If you have an reoccurring event scheduled and you use the week view to drag the event to a new time slot to reschedule it, and select "This event only", the event will update its scheduled time and date, but will still show in the same time slot in the day view.

STEPS TO REPRODUCE
1.  Schedule an event that reoccurs on the same day each month.
2.  Open the week view and locate the reoccurring event.
3.  Drag the event to a different day of the week. When asked if you want to make the change to just this event or all events, choose just this one event.

OBSERVED RESULT
The month and week views show the event moved to the new time and date. 

The day view will show the event as it was previously scheduled. Hovering over the event will show a tool tip style window that displays the correct rescheduled time and date. Printing the day schedule will still show the event.

EXPECTED RESULT
The day, week, and month views of the calendar should all reflect the events. 

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: openSUSE Tumbleweed 20240915
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.9-1-default (64-bit)
Graphics Platform: offscreen


ADDITIONAL INFORMATION
I have noticed this issue in earlier releases but didn't put the time into researching it.