View Single Post
That would be a definite plus:

In real world, a task or anaction is defined by a priority if due in the future, a person responsible / necessary to the task, some extra resources, location, and some more such as a reference to the kind of action performed (phone call, email, etc).

No matter what you do, at one point you will bump into the trouble of assigning a single context to an OF task while you would need several.

You can work around for a while, but that always seems to be like a sort of hack. Besides making things clean, it would keep focus on performing the tasks and not on managing the list in OF (which is why I personally find OF superior when not needing multiple contexts).

In addition, I would need these multiple contexts (or tagging capabilities, call it the way you want) for reporting: OF is a document repository for me, as well as a holding the minutes of meetings, keeping track of business lunches and so on. I now want to be able to review the efficiency of my different actions, the way projects get accomplished... and for that I need a better way of tracking the attributes of tasks / actions as explained in the 1st paragraph than having a single context.

That makes things more complicated, but is it finally to complicated to use # with twitter or gmail tags?