I've been an avid user of the Android app for 6 months or more. I have a question and perhaps I'm just not using it right, so I'll ask the braintrust. I usually use the Action screen, with a tag filter to filter by current context. So when I make a new action, it defaults to my tag (context). That's great, but when I want to set a project for my new task, it only shows the projects that match the filter. So, in order to make my project show up in the dropdown when I'm adding a new action in context "Office", my project also has to have tag (context) "Office". That strikes me as odd and not GTD-ish. Projects don't have contexts. They are just a big old list of projects.
Similarly, when I switch to the wait screen, I only see Waits that match the filter, so again, my Waits have to have a context, which is a bit inconvenient, and it's easy to lose a wait because it didn't have the right tag to show up.
It seems to me that only Actions should have tags, or perhaps only the Action screen should use the tag filter?
In ActionComplete actions, waits, projects, and ideas are different types
of tasks. Actions are active atomic tasks (actionable items), waits are
delegated tasks, projects are composites that contain subordinate tasks
(actions and waits), and ideas are deferred tasks you are decided to not
act upon right away. All types of tasks exist within a context - or several
contexts - defined by metadata (tags, people, and places). Tags are by far
the most frequently used context markers. They can be anything that makes
sense to you and meaningfully splits your tasks into manageable buckets.
Kind regards,
Borys Burnayev
ActionComplete
Your Streamlined GTD Toolkit
But you could easily have a project that has actions in multiple contexts (A and B). So, if you put the project in context A, then when you filter by context B and decide to add an action for that project, the project won't appear in the dropdown because you are filtering by context B but the project is in context A. You'd have to remove the filter to get the project to show up.
On Wednesday, July 18, 2012 9:57:55 PM UTC-4, Borys Burnayev wrote:
> Dan,
> In ActionComplete actions, waits, projects, and ideas are different types > of tasks. Actions are active atomic tasks (actionable items), waits are > delegated tasks, projects are composites that contain subordinate tasks > (actions and waits), and ideas are deferred tasks you are decided to not > act upon right away. All types of tasks exist within a context - or several > contexts - defined by metadata (tags, people, and places). Tags are by far > the most frequently used context markers. They can be anything that makes > sense to you and meaningfully splits your tasks into manageable buckets.
On Fri, Jul 20, 2012 at 4:52 PM, Dan <daniel.han...@gmail.com> wrote:
> But you could easily have a project that has actions in multiple contexts
> (A and B). So, if you put the project in context A, then when you filter by
> context B and decide to add an action for that project, the project won't
> appear in the dropdown because you are filtering by context B but the
> project is in context A. You'd have to remove the filter to get the project
> to show up.
