+ 1
(This feature has also been referred to, in other threads, as "hierarchical" contexts)
Further, I suggest that the Context and Tag features be "integrated" (harmonized), such that contexts be a subset of the tags, used for listing/grouping purposes, whereas tags in general can be overlapping (more than one per task).
Enabling users to assign context under other context. Essentially with a nested context folder the user can achieve the benefit of having a very clear top-level context list. This is especially helpful for more powerful users when the number of contexts start to get beyond 20.
- tasks assigned to child context will also be assigned to parent context
- users can browse further to cover all the fine details.
A typical user scenario, where you have a workplace context, and multiple contact person under that context, and maybe a meeting context as well. So all work-related things are assigned to the top-context (workplace), and related topics are assigned only to the specific person (as a child context), or the meeting (another child context).
-
12/15/2014 19:50#1PRO
-
12/16/2014 07:17#2PRO
@Folke @zmfile04
Hi,
Thank you for your feedback.
We have recorded your suggestion. We will take it into consideration.
Shall you need any help or have additional questions, please do not hesitate to contact me back.
Thank you for your support!
Best regards,
Doit.im Team -
12/16/2014 07:41#3PRO
@Folke, you're amazingly everywhere.
Goal, project, context, tag, task ... doit has more concepts than most other GTD tools and may be over-designed. So I definitely think merging tag and context is a welcoming idea. But on a conceptual level, you can do more with tags than context, and the way doit currently use tags to categorize task entries for big projects lives in a very different UI space (more passive as a filter) than context (more active, where you want to fire and just see a list right away)