Quote:
Originally Posted by pjc
3) But, frankly, I can see the use for making the singleton bucket behavior more like a normal project, i.e. only the first single task should be considered the "next action". (This is handy when the singleton task list grows very very large and begins to overwhelm your context view.)
|
I think the vision of singleton actions is as single-step tasks that are independent of each other. If that's the case, why would you consider only one of them as a next action i.e. something you can move on now?
Quote:
Originally Posted by pjc
I realize regular projects behave like #3, but I can't tell the inbox to shuffle projectless tasks into a regular project.
|
That'd be because they aren't part of a project until you assign them one, wouldn't it?