Version: (using KDE 3.5.8) Installed from: Ubuntu Packages The current behaviour of recurring ToDo items is unintuitive. Currently, when one marks a recurring ToDo item as 'done' it's Due Date is simply pushed forward one recursion period. The Complete field remains at 0% and no checkmark appears in the checkbox. Also, although the item is completed for it's recursion period, it still appears in the Summary view. In my opinion, a recurring item is 'done' until the recursion period resets. It then becomes undone. If I need to check my postal mail once a week, then on Sunday I expect the "Check Postal Mail" item to be unchecked. When I finally get around to it on Thursday and mark the item 'done' I expect it to stay done. Until next Sunday. Therefore, I propose that items marked as 'done' have their completion status changed to 100%. Only when the recursion period ends should the completion status be reset to 0%. Advantage of this method: 1) In summary view, ToDo items that are currently marked as 'done' will not be shown. 2) In ToDo view, one could see at a glance (via checkmarks and completion status bar) which items need to be done. 3) The UI becomes more intuitive and provides visual feedback when checking an item.
I request that this be implemented or at least that the start date also be updated along with the due date when the task is marked complete for the current period. It is silly and makes no sense and is rather confusing when the the task continues to appear in the summary view after having been marked as complete for the period.
I second this request although I think that the new feature should be configurable somehow, especially in the Todo List. As discussed on the kdepim-users, we're finally in front of an alternative where we have to privilege either the done recurrence (what Dotan asks for) or the next to come recurence. Some users may find useful the current behaviour since it privileges the "things-that-are-still-to-be-done", rather than "things-that-are-done-for-the-moment-even-if-they-will-recur-in-some-time", I mean there are legitimate use cases where one would prefer the Todo List presents the next to come recurrence although one have not yet entered its "life-span" (which is the current behaviour), hence ignoring the "current and/but done" recurence.