I'm a little confused.. is the hesitation based on how to make it work or whether it is part of GTD?
As far as how to make it work, it sounds pretty straightforward:
You just have to make the context choice a list box instead of a drop-down box. This way, you could select multiple contexts while only having one action entry exist on the project side of things.
If it's a problem of deciding whether this stays true to GTD, then I'm not sure what to think on that side of things. I imagine a purist could stick to just the one context for each action but as some have pointed out, some actions do apply in multiple contexts. It's just a matter of making sure that if it is checked off in one context, it applies to all (this shouldn't be a problem if everything is being pulled from a database which I believe it is).
As far as how to make it work, it sounds pretty straightforward:
You just have to make the context choice a list box instead of a drop-down box. This way, you could select multiple contexts while only having one action entry exist on the project side of things.
If it's a problem of deciding whether this stays true to GTD, then I'm not sure what to think on that side of things. I imagine a purist could stick to just the one context for each action but as some have pointed out, some actions do apply in multiple contexts. It's just a matter of making sure that if it is checked off in one context, it applies to all (this shouldn't be a problem if everything is being pulled from a database which I believe it is).