[korganizer] [Bug 474312] New: Recurrent tasks' start- and due-date isn't updated in todoview and agendaview when deleting old entries

[kero]

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

            Bug ID: 474312
           Summary: Recurrent tasks' start- and due-date isn't updated in
                    todoview and agendaview when deleting old entries
    Classification: Applications
           Product: korganizer
           Version: unspecified
          Platform: Archlinux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: recurrence
          Assignee: kdepim-bugs at kde.org
          Reporter: keikoz at free.fr
  Target Milestone: ---

Hi,
When I create a recurrent task, and then delete an occurrence (let's say, the
first one, because the task is done), this occurrence becomes an "exception" in
the task's "Recurrence" view.
But, the start- and due-date doesn't change in the todolist, which could be
seen as inconsistent. This leads at least to two problems:
- in the todolist, the tasks appears with red background (as for all old undone
tasks), as a reminder. That could be acceptable, but still more annoying:
- in the agendaview, the "undone" task's occurrence is listed among current
day's tasks, even if in fact, that occurrence was marked as exception by
deleting it.
Hence, I think that when handling recurrent tasks, korganizer should internally
define a start- and due-date which takes in count the existence of exceptions.

Regards

STEPS TO REPRODUCE
1. Define a recurrent task
2. Delete the first occurrence

OBSERVED RESULT
Todolist still show the former start- and due-date and agendaview shows the
task as undone.

EXPECTED RESULT
Todolist and Agendaview act as if the start- and due-date changed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Archlinux
KDE Plasma Version:  Not using Plasma at the moment (using kde-pim over XFCE)
Qt Version: archlinux package: qt5-base 5.15.10+kde+r152-1
Korganizer version: Version 5.24.0 (23.08.0)

-- 
You are receiving this mail because:
You are the assignee for the bug.