Yes. I haven't thought of a good way to handle this yet, because of the way that the database table is structured.

hmm, yes, that would be a great idea.
But AFAIR from other projects it's not an easy task.

What about integrating some kind of "tag capability" what probably could solve different feature requests in once? (yes I know that this wouldn't be easy either...)

I've read something recently about tagging, so this might be a good way to go.

for me it turned out in the past, that at some point I always stumble over "tags" because they seem to be the perfect workaround against things getting too complex...

The question probably coming up at this time: "should tracks be considered a GTD application_' or a '_project management (with GTD capabilities)?" Everything between IMHO might attract lots of interest but will either lead into endless feature requests or blow the interest away for the lack of simplicity.

I don't know enough about ruby and rails, but probably this might be helpful somehow: " googled@bigbold.com/snippets for ruby rails tagging":http://www.google.com/search?num=100&hl=en&lr=&as_qdr=all&q=ruby+rails+tagging+site%3Abigbold.com%2Fsnippets&btnG=Search?

doesn't that "nice rails application (Snippets)":http://www.petercooper.co.uk/archives/000818.html @bigbold.com itself already provide a "tagging feature" which is useful to look into...?

last posting was from me, Firefox did just forget my name somehow ;)

Need for this is mitigated by tagging feature. Closing.

Duplicated association with ticket #375 was added

Is it really mitigated by tagging feature? Should tags be used as contexts? As I continue to use Tracks I will investigate. But one thing is clear. Contexts are Contexts. Tags are not Contexts. If we intend to use Tags as Contexts, then we should get rid of the existing contexts and rename the Tags into Contexts.

I see the use of Tags, of course. No doubt about it. But it does not replace having the ability to put a Task into multiple contexts (a feature which I'm not sure I need).

For the example of why I should have multiple contexts, is that I can contact someone on the phone or in an e-mail message. Then I would want to put my task into the Phone and Computer contexts.