Bug 246908

Summary: edits on due times of periodic todos get lost when marking them as completed
Product: [Applications] korganizer Reporter: Toomas Rosin <toomas>
Component: todoviewAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: toomas
Priority: NOR    
Version: 4.4.5   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Toomas Rosin 2010-08-06 14:39:26 UTC 
Version:           4.4.5 (using KDE 4.4.5) 
OS:                Linux

When I edit the "due time" field of a periodic todo and afterwards mark the todo as completed, its due time changes back.


Reproducible: Always

Steps to Reproduce:
File->New To-do
Set "Title" to "test".
Check the "Time associated" check box.  Set "Due Time" to (e.g.) "15:00".  Don't check "Start".
Go to the "Recurrence" tab and check the "Enable recurrence" check box. Set other values as appropriate.
Choose "OK" to save the todo.
Double-click the newly created "test" todo in to-do view.
Everything is correct: "Start" is unchecked, due time is "15:00".
Set "Due Time" to "14:45".
Save the todo again by choosing "OK".
Double-click the todo again.  Now, the "Start" check box is checked and start time has been set equal to due time.
Mark the "test" todo as completed by clicking the check box on its left.
Double-click the todo again (it has probably moved).  Now, "Start" is still checked, start time is "14:45", but the due time has reverted to "15:00".


Actual Results:  
After editing due time, "Start" has been automatically checked and start time is set equal to due time.
After marking the todo as completed, "Start" is checked, "Start Time" has still the value "14:45" I set for due time, but the due time is "15:00" again.


Expected Results:  
After editing due time, "Start" should have remained unchecked.
After marking the todo as completed, "Due Time" should have retained its manually set value "14:45".


OS: Linux (i686) release 2.6.34.1
Compiler: gcc

I have observed this behavior at least since 3.5.9.
Comment 1 Denis Kurz 2016-09-24 18:46:18 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:15:41 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.