Hi!

I wrote this with the Next folder in mind, but my comments apply to not only the Next folder, but also the Waiting and Someday folders.

I very much like the Next folder, as I can put tasks there to temporarily get them out of the Today folder so that my Today folder can help me focus my attention on just my most pressing 7 +/- 2 tasks (the Doit.Now feature helps with this as well).

However, if I move a task to the Next folder, it's start time becomes "Next". Then, when I move it back to the Today folder, its start time changes to today (and if I move it to the Schedule folder from the Next folder, Doit.im asks for the date, rather than remember what the assigned start date was before the task was moved into the Next folder).

This effectively means that using the Next folder = information destruction (i.e., a "Bad Thing"). So, I stopped using it long ago for this reason, as I need to know when I entered a task into Doit.im (and I need that date to NOT change, EVER).

In a highly-exploratory, constantly-changing task environment such as mine where new incoming tasks are constantly arriving and many are not acted on because more action paths are proposed than are ever acted upon, knowing the "age" or "staleness" of a task is critical information in assessing if the task is to be kept, completed, or deleted. But using the Next folder destroys this information, which I consider to be be a bug.

So, I'd be most grateful if someone could look into this and see if there's a way tasks placed into the Next and Waiting and Someday folders can "remember" their original start date when the same task is later moved again out of the one of those folders and into some other folder (e.g., to the Today or Scheduled or Waiting folder). In other words, this "remembering" of the original task start date should persist, and ONLY change when the user explicitly changes the start date (even if it is not visible in these "dateless" folders like Next, Waiting, and Someday).

Principle: Don't destroy user's information unless the user explicitly requests it or unless the user has been clearly warned beforehand that a given action might result in information loss.

Thanks!
Doug