Quote:
Originally Posted by omnibob
So far the vast majority of Actions I have that are waiting for have a Context that is known up front. "Order widget X." @computer [waiting for budget approval]; "Go for walk on beach." @errands [waiting for sunny day]. So for me, I'd rather have it entered up front, but I can see this isn't the case for everyone. Still, having a "WF" or "WF- Electrician (or someone like him)" is a handy way to filter; it would be interesting to have a second Context assignable to an Action, sort of queued up that would take over when the WF is done. Go ahead, throw the beer bottles this way, I'm surrounded by chickenwire! ;)
|
It sounds like you're actually talking about actions grouped into a project. At least that's how I'd do it. The "Get a Widget" project might start with three actions: ask for approval (context: phone), receive approval (context: waiting, which is set to on-hold), and purchase widget (context: errand).