Quote:
Originally Posted by HappyDude
1st: I don't particularly enjoy going through each one of my projects under projects to see if anything else is still in there that needs to be completed that didn't make it to the contexts area; I do place all my actions with a context but I still go through each project looking to see if anything was missed.
|
An easy way to look for actions missing a context is to flip over to context mode and click on the "No Contexts" container at the top. That will show you all the actions which have -- wait for it -- no context assigned. As long as you haven't set your view bar options so that it won't show you everything (like only looking at completed actions, or contexts that are on hold, or ...) you should be able to quickly spot any actions missing a context. If you do find an action missing a context, double-clicking the row handle will get you a new window focused on the project that contains that action, so that you can fix the context, well, in context :-)
Quote:
But more importantly this question falls more under how to mark a project as being completed or dropped or whatever, once all of the actions within the project have been completed? As of now i'm going through all my projects one by one and will notice a project that no longer has any actions in it, since i've completed them all. Therefore the project has been completed and I right click the project title and mark it as "complete" but hate having to scan through all my projects looking for a project with no actions to tell me i'm done with that project..
Is there an alternative i'm missing in this regard? Without having to riffle through my projects ? Better yet is there a way the project itself automatically can consider itself as completed once all actions inside of that project have been completed?
|
There's an option to make a project or action group mark itself complete automatically upon completing all of the contained actions. It's in the Inspector, near the top. There's also an option in the preferences to make this be on by default. I'd encourage giving some thought and observation to how often you would need to be watching out for the "other case" regardless of how you choose to set this option. I find it to be a handy option, but don't have it on by default, because I often don't plan my projects out entirely before commencing work and thus I don't want a project marked completed before it should be.
Quote:
I pulled up these 3 views with "completed" actions (to view what I had already accomplished). The three variations consisted of seeing these finished steps in views of:
1. Context: Where they were completed.
2. Project: Just what exactly had been done towards the finalization of an array of projects.
3. Completed: Which shows actions completed the same day, yesterday and within the last week.
I enjoy the context look to determine how much I GTD'd or slacked off at a particular location, and the project context one is interesting and the completed view shows me I got more done today than yesterday, though today's tasks were minor ones while yesterday's were bigger important tasks.
|
My "completed" view is context mode, grouped by completed (with all triangles except "Today" closed), sort by project, completed actions, any duration, any flag. Most of my work (at least by action count) is drawn from repeating actions, many of them in Single Action Lists, and so I don't have as much project focus as others might. If I had to report to someone, there would probably be more project orientation. If I had to report my doings in chronological order, I would change the sort to completed.