102 votesUllrich Jans commented
The way it looks to me at the moment, running version 0.0.96, is that new tasks created via Quick Tasks get created in the current context (or the first one selected when selecting multiple contexts).
This clashes with the GTD idea, IMHO, since the whole point is to minimize interruptions and dump them into the inbox as quickly as possible and process them later.
This functionality should probably be configurable, since there seem to be other people who want new Quick Tasks to appear in the current context (I can see their point, too!).
Case in point: I'm at work, so I select context @work. I get a call from a friend/colleague if I can lend him something (e.g. USB power meter) which I happen to have bought a while ago. So I create a quick task to pack that device. It shows up in the @work context, forgotten when I get home and switch to the @home/@computer/@errands contexts. I show up at work, switch to the @work context, oops, I forgot to pack the device since it didn't show up in the Inbox (which keeps conveniently empty...). That is not the goal of GTD!
Thanks Thomas for reporting this issue.
I agree that there is an inconsistent behaviour, but the point to be clarify is about “What’s wrong?”:
option 1: the active filter should filter the inbox list result
option 2: new tasks added from the iinbox list should ignore the active filter in terms of default values
You are suggesting to go for option 2 but I’m not sure it’s the most appropriate.
Could you please motivate your choice and try to convince me?Ullrich Jans commented
This is an issue for me as well. I frequently add new tasks that are inappropriate for the current context, only to have them show up in the context, having to go back and kick them over to the appropriate one.
Maybe I'm doing it wrong, but I tend to select one or more contexts when I start working on the tasks there, then, as proposed by the GTD concept add things/interruptions that pop up as quick tasks, expecting them to end up in the inbox to be processed later.
I think this should be at least configurable, as it interrupts my workflow and goes against the GTD idea, which is to deal with interruptions by dumping them into the inbox, to be processed later.