Bug 121853

Summary: Task repeats after beeing done
Product: [Applications] korganizer Reporter: Claudius Wettstein <claudius.wettstein>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: alexngould, groenem, smartins
Priority: NOR    
Version: 3.5   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Claudius Wettstein 2006-02-12 23:35:55 UTC 
Version:           3.5 (using KDE 3.5.1, Kubuntu Package 4:3.5.1-0ubuntu0breezy1 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.12-10-386

In Outlook, there is an option for repeating a task "x days after beeing done"; so if solving a task is delayed, however the next repetition occurs x days later. Would be a great feature for korganizer, too.
Comment 1 Reinhold Kainhofer 2006-11-02 19:30:27 UTC 
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 2 Bram Schoenmakers 2006-12-21 14:28:01 UTC 
*** Bug 139087 has been marked as a duplicate of this bug. ***
Comment 3 Marius Groenewald 2007-05-28 13:22:52 UTC 
When I create a Task and set it to recur every 56 days, it works if I Complete the task on the specified date. 
However, if a few days goes by before I can Complete it and I mark it as Completed, say 7 days after the Due Date, the next due date is not 56 days, but 49 days. 
Kontact should have an extra setting to allow you to select, that the amount of days specified in the Recurring tab, should start after the Task is marked as Completed or not (56 days after the date marked as Completed).
Comment 4 Marius Groenewald 2007-05-28 13:27:22 UTC 
Another thing. If the Due date was example 28 May, but I mark it as Completed on 31 May, it shows in the Calendar that the To-Do was Completed on 28 May, instead of 31 May.
Comment 5 Alex Gould 2009-01-23 17:11:13 UTC 
This may be a duplicate of bug 46573.
Comment 6 Sergio Martins 2011-03-18 00:27:42 UTC 

*** This bug has been marked as a duplicate of bug 46573 ***