Quote:
Originally Posted by Ken Case
OmniFocus does have a notion of project status: a project can be active, on hold, completed, or dropped, and you can filter the project list using these states. You can also set start dates on projects and actions (giving you a "scheduled" state), and you can create different top-level folders for projects and use those to create your own arbitrary groupings of folders (such as a someday/maybe list, which might be a bunch of projects in an inactive folder).
|
If my understanding of contexts is correct—that it is "what you can do, where you are, with the tools available"—then "Waiting for" is not a true context and asking the context system in OmniFocus to handle waiting-fors is to knock a hole in the hard wall of that definition. But then if not a context, how should such tasks be identified? One might point to "On hold", but are such tasks really on hold, or are they active but just being active elsewhere on someone else's desk?
Does the inclusion of a scheduling system in OmniFocus (start date, due date) mean that "waiting for" is no longer a useful state to recognise? Does the hole in the context wall really matter?