I'm sure the answer to this is in here somewhere, but I can't find it ...
I want a category for actions I've cancelled, but want to keep in the database because they may be useful when a similar job comes around again (most of my actions are to do with contacts).
So I create a "Cancelled" context with status "Dropped", on the expectation I'll just file such actions into this category. That's possible in the Context pane - I can drag and drop. But in the Projects pane, I can't access the "Cancelled" category via the context drop-down or the contextual menu.
I can see the point - if you've got a stack of redundant "dropped" contexts, you don't want them appearing everywhere. But at the same time, it's a bit of a barrier to flexibility. Is there a middle road - a "dropped-but-visible" context mode?
Matt
I want a category for actions I've cancelled, but want to keep in the database because they may be useful when a similar job comes around again (most of my actions are to do with contacts).
So I create a "Cancelled" context with status "Dropped", on the expectation I'll just file such actions into this category. That's possible in the Context pane - I can drag and drop. But in the Projects pane, I can't access the "Cancelled" category via the context drop-down or the contextual menu.
I can see the point - if you've got a stack of redundant "dropped" contexts, you don't want them appearing everywhere. But at the same time, it's a bit of a barrier to flexibility. Is there a middle road - a "dropped-but-visible" context mode?
Matt
Threaded Mode