2009-03-25, 05:24 PM
Creating one (or several) contexts that are in the On Hold state and assigning actions to that context is a popular approach.
Here's what I prefer, though: I have contexts for the various folks I work with, so I don't have actions like "email Steve about secret lair". I know who it's for from the context, so I just have an "email about secret lair" action.
Once it's done/delegated, I bump the start date and add "check on " to the action name. The future start date keeps it off my active list until that date rolls back around, at which point it pops back on automatically.
This works for me, without requiring a separate context to hold those actions I'm waiting on. They just stay in the context for the person the task was handed off to.
Last edited by Brian; 2010-05-04 at 01:48 PM..
Reason: clarify my method a bit