Michael Done

Further to my reply to Scott T ... A fairly straightforward design adjustment to accommodate my needs would be that when a recurring task is marked as complete, Evernote doesn't immediately update the due date on the repeating task, but instead proceeds in two stages: 1. It clones the recurring task, setting the clone as a non-recurring task with its due date set to the current date of the recurring task (i.e. the as yet un-updated due date) and with a status of completed. Note: If the user ever comes back and marks this completed task as incomplete, then (provided no later occurrences have since been completed), the recurring task due date is set to the due date of the clone, and the clone task is deleted. 2. It updates the due date of the recurring task to the next due date.

Thanks, Scott T. My suggestion is that your team develop the facility to show completed individual instances of a repeating task in the 'completed tasks' view. It seems clear to me that a recurring task is treated by Evernote as a single object/entity. Effectively, Evernote forgets about all past occurrences of a recurrent task. It simply updates the due date of the recurring task, then shows it (of course) as incomplete. This approach gives me no useful history of completed work. Please ask your developers to look into capturing, saving and reporting completed instances of recurring tasks. This would turn repeating tasks into a gorgeous feature. At the moment I'm having to set up recurring tasks as a set of manual non-recurring tasks, so that I can see an accurate story of what work has been done. This is disappointing and frustrating for me, and a sad waste of the potential of recurring tasks. Thanks a lot ... Michael.