Originally Posted by whpalmer4
IMO, this is not intended for use as you suggest, working on one project to the exclusion of all else, but rather to make it more quickly apparent that a project (or action group) has had all of its predetermined actions completed so that it can be immediately marked complete, if appropriate, or fleshed out further, without having to wait for a review to catch the now-empty project or action group.
That makes more sense. However, that's not what I'm seeing, unless I have a VERY specific set of filters set up in Context view. Otherwise, I get projects lumped in with everything else, with no information to tell me whether the project is completed or not.
And, truly, what context should the "Wanna check off the project for good?" action/project/item exist in? Per my earlier post, projects don't really belong to any given context -- the assignment is fairly arbitrary -- so there's no guarantee that the project will "pop up" per your example. It is just as likely to pop up in another context entirely, again, leaving me without the information I need to know whether the project's still open and has actions, whether it's stalled, etc...
A more useful approach would be to add a "Yay! You're done!" next action to the end of every project, reminding you that it's time to close the project.
And I have to ask: What's the harm in having an empty project that's actually been completed? Until you're in Project/Planning mode, it won't get in your way at all. And once you are in that mode, well, then you have all the information you need to appropriately check off or add actions and extend open projects.
And, to be sure, checking off a project is NOT an action in and of itself. It's just a record keeping activity to clear off your list of "open loops." So, again, it doesn't belong in "Action Mode."
Workflow-wise, it would make more sense to have a special view for projects which have no more available actions. Something like... I dunno... "Stalled Projects." ;)