[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=345565

gjditchfi...@acm.org changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/fram
   ||eworks/kcalendarcore/commit
   ||/dc7b1865c3bff04d0173505335
   ||da22cefa3b5f5f
 Resolution|--- |FIXED

--- Comment #6 from gjditchfi...@acm.org ---
Git commit dc7b1865c3bff04d0173505335da22cefa3b5f5f by Glen Ditchfield.
Committed on 10/06/2020 at 15:17.
Pushed by winterz into branch 'master'.

Fix serialization of recurring to-do's start date

KCalendarCore uses Todo::Private::mDtRecurrence to hold the start date
and time of the next uncompleted occurrance of a recurring Todo, and
deserializes it from the X-KDE-LIBKCAL-DTRECURRENCE property of iCalendar
files.  However, ICalFormatImpl::writeTodo() serializes dtDue() into that
property, not dtStart().

When KOrganizer creates a new recurring to-do, it serializes the to-do,
then deserializes it to populate the To-Do List view, so the view shows
an incorrect start date (and an incorrect due date, which is calculated
from the start date).
Related: bug 345498

M  +1-0autotests/CMakeLists.txt
A  +83   -0autotests/testdateserialization.cpp [License: LGPL(v3.0+)]
A  +19   -0autotests/testdateserialization.h [License: LGPL(v3.0+)]
M  +2-3src/icalformat_p.cpp

https://invent.kde.org/frameworks/kcalendarcore/commit/dc7b1865c3bff04d0173505335da22cefa3b5f5f

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[Karsten de Freese]

https://bugs.kde.org/show_bug.cgi?id=345565

--- Comment #5 from Karsten de Freese  ---
It appears that the problems can be worked around under specific conditions:
- have start & due dates on the same day (e.g. via different times)
- save the to-do before entering the recurrence

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[Karsten de Freese]

https://bugs.kde.org/show_bug.cgi?id=345565

Karsten de Freese  changed:

   What|Removed |Added

 CC||kars...@maxi-dsl.de

--- Comment #4 from Karsten de Freese  ---
still an issue with Korganizer 5.12.3 (I'm using Tumbleweed)

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=345565

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #3 from Christoph Feck  ---
Thanks for the update; setting status.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=345565

gjditchfi...@acm.org changed:

   What|Removed |Added

Version|unspecified |5.4.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=345565

--- Comment #2 from gjditchfi...@acm.org ---
The bug still exists in Korganizer 5.4.3, embedded in Kontact.

On 2017-07-02, in Kontact's "To-do List" tab, I selected an old recurring
to-do.  Kontact's to-do summary showed a start date of 2016-04-18 and a due
date of 2016-04-25.

I opened the todo, and the dialog showed start date 2014-07-17, due date
2014-07-24, repeats monthly, every 1 month, on the 17th.

I closed the dialog, and clicked the check box in Kontact's summary list.

Actual results: the summary start date changed to 2017-07-24, due date
2017-07-31.

Expected results: start date should be 2017-07-17 and due date should be
2017-07-24

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 345565] completed recurring to-do recurs on wrong date

[Denis Kurz]

https://bugs.kde.org/show_bug.cgi?id=345565

Denis Kurz  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Denis Kurz  ---
This bug has never been confirmed for a KDE PIM version that is based on KDE
Frameworks (5.x). Those versions differ significantly from the old 4.x series.
Therefore, I plan to close it in around two or three months. In the meantime,
it is set to WAITINGFORINFO to give reporters the oportunity to check if it is
still valid. As soon as someone confirms it for a recent version (at least 5.1,
ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for
versions almost two years beyond their end of life.

-- 
You are receiving this mail because:
You are watching all bug changes.