[Akonadi] [Bug 446216] New: Due date changes for todos not being saved, for fresh todos due date rolls back to previous day
Claudio Cambra
bugzilla_noreply at kde.org
Sun Nov 28 23:42:12 GMT 2021
https://bugs.kde.org/show_bug.cgi?id=446216
Bug ID: 446216
Summary: Due date changes for todos not being saved, for fresh
todos due date rolls back to previous day
Product: Akonadi
Version: 5.18.3
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Google Resource
Assignee: dvratil at kde.org
Reporter: claudio.cambra at gmail.com
CC: kdepim-bugs at kde.org
Target Milestone: ---
Created attachment 144051
--> https://bugs.kde.org/attachment.cgi?id=144051&action=edit
Video of bug in Kalendar
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Adding a new todo within a Google calendar has bugs regarding the due date.
When a new todo is created and it is set to have an all-day due date, when the
collection refreshes the date will be rolled back to the previous day.
If one tries to edit the due date for a task, the edit will be reverted once
the collection refreshes.
Can reproduce on both Kalendar and KOrganizer.
STEPS TO REPRODUCE
1. Create a new task within a Google Calendar
2. Assign a due date and save
3. Wait for the parent collection to refresh automatically or manually refresh
and see the dates get rolled back to the previous day
or...
1. Edit a task's due date and save the changes
2. See the dates revert to their previous due dates upon refresh
OBSERVED RESULT
Todos' due dates change on calendar refresh.
EXPECTED RESULT
Todos' due dates should remain the same as the user has set them.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
I have attached a video showing the issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Kdepim-bugs
mailing list