Quote:
Originally Posted by joelande
I placed my @Waiting context "On Hold" by unchecking the "Active" status in its contextual menu (or so I thought).
However that prevents the ability to assign an action to @Waiting.
Hovering over the inspector button shows that the context is not on hold, it is "dropped".
I guess I should have figured that out - instead of the "pause" badge, it had an "x" badge.
So - how do people handle @Waiting - just assign the @Waiting context, and leave it active, and know it really isn't?
|
Are you talking of an earlier build? I just checked this, and I able to assign an action to @Waiting when it is 'On Hold'. And anytime i give an action the context @Waiting all future actions (for sequential project) become unavailable as they should. Am I misunderstanding something?