Why, after an task is marked done after midnight, isn't "every day" generating tasks properly?
I have a task that must be repeated "every day" and the due date is set to "every day". Sometimes the task is done after midnight on the day it's due, making it overdue, because that's the nature of the task. However, when I mark it "done" and a new task is generated, the new task lands in tomorrow's list of tasks, not today's. This is incorrect. It should be placed in today's task because the recurring nature of the task *should be* based on when it was due (since we're after mid-night, yesterday), not when it was done. Therefore the newly generated task should show up in *today's* list of task.
If I had used "after 1 day" then, yeah, the date should be calculated based on the done date, today, and placed in tomorrow's list.
I just recently move over from RTM after using it for many years because of a number of things I prefer about TD (primarily the UI). However, this bad date calculation (which RTM does correctly) could become an issue. I assume the invalid date calc is done on all "every x days" that are marked complete when overdue.
Your documentation and I agree: "after 1 day" and "every 1 day" are not the same. Please fix ASAP.
P.S. As an aside, I think combining the due date and the recurring formula in the same field is dangerous and isn't the best design choice. If I want to move the current due date of an item that has a, for example, "after x days" recurring pattern, I shouldn't have to juggle those two data elements in one field. Again, not that RTM is the superior product in most other areas, but they get it right on this point as well.