At the risk of beating a dead horse here, I wanted to pose this question once again now that I'm back up on the latest trunk revision and still don't see this feature...
Why must all todos have a context associated with them? How do people using tracks deal with actions that you've entered on a project, but don't want to see them yet in your context list on the homepage? Say I create a new project: Implement Home Firewall... I can start loading the project up with tasks I know need to be done, but only 1 or 2 or so of these are immediately actionable, and only those do I want to see in my contexts... the rest of the actions are just noise at that point. In the past in tracks, I've created a placeholder context, "hold", that I would assign to tasks like these so that they wouldn't clutter up my home page. What's the sanctioned way of dealing with this problem? BSAG and Luke, how do you guys work your system. Am I the only one running into this? My interpretation of GTD is that during my reviews I would move tasks from my project to my contexts when they become actionable, but that I could still keep track of tasks that have dependencies in terms of my projects. Let me know what you all think and again, forgiveness in advance if I'm resurrecting a horse that's already been severely bludgeoned. G _______________________________________________ Tracks-discuss mailing list [EMAIL PROTECTED] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
