Comment 88 for bug 307680

Revision history for this message
In , Benjamin Kraus (ben-benkraus) wrote :

You are correct that the logic in comment #31 requires you to mark a recurring task as complete before the next recurrence, but it doesn't have to stay marked complete. Perhaps this isn't the best solution, but if you find yourself in the scenario described in comment #35: When you decide to complete August's sales tax report you simply mark June as complete then mark it as incomplete again. Upon marking it as complete, it will generate a new task for July, but leave behind the task for June as an isolated task which can be modified as you please. So, the complete set of operations would be:

1) Mark June as complete then immediately mark it as incomplete.
2) Mark July as complete then immediately mark it as incomplete.
3) Mark August as complete (assuming you've finished August's report)

The result is regular (incomplete, non-recurring) tasks for June and July, a completed task for August, and a new recurring task for September. This is how I used to use Outlook before I switched to Lightning, and it worked out nicely (and having to go though those steps reminds me just how far behind I was on my recurring tasks).

- Ben