Hi,
I have read in another thread that most users use a "waiting" context with a "on hold" status where they put all the actions in that requires an action from someone else.
I have done this as the user "keone" described it in another thread.
Quote:
I have a [single] "Waiting For" context setup in my context lists.
So, let's say that I have an action with a "Phone" context. I make that phone call on the prescribed date, but now need to wait for something back from the person I called in order to move the project forward. I briefly write down a summary of the call in the note section under that "Phone" action, and then change the context to "Waiting For" with a due date of, say, three days out.
Now, three days later when I'm in context view I can readily see that a red badge next to my "Waiting For" context indicates that I have one item due. I click on the "Waiting For" context, and there it is, a recap of that phone call of three days ago. Since I haven't yet received whatever it was I was waiting for,
I now have three choices: a) Call that person to follow-up; b) Bump the due date forward another two or three days; or c) Ignore it and let the action sit there in red until I do something with it.
|
My problem, however, is that if I use a due or start date on the action so it shows up again under Context view as user "keone" desribed, it won't. It only shows up when I select "Remaining" under view and not "Available".
Is there any trick to this I'm missing?