Nested Projects or Contexts | Help Center

Nested Projects or Contexts

PRO

bhkiv 09/20/2013 15:36

Platform:AllCompleted

One thing that is really nice about some other TODO systems (toodledo, flow, etc) is the ability to nest projects/lists/contexts/etc

I have many different work projects and as any long term project does, they have many sub projects/features

Using contexts is useful but does not cover fully all of the use cases I have and prevents me from organizing things in a logical way

I can of course use tagging but that degrades is use for other more categorization based organizations of tickets between multiple other types of grouping (ie between projects, goals, contexts)

Are there any plans to add the ability to nest any of the groups

bhkiv post on 09/20/2013 15:40#1

PRO

I would expect it to be pretty easy to add a recursive parent id to the project table and then simply alter the left nav display and the searching/listing functions
Folke post on 09/20/2013 16:34#2

PRO

+1 Nested and interrelated projects is a hugely important feature, and I do not believe it is difficult to implement. http://help.doit.im/topics/1617

and +1 for nested Contexts (Tags, Labels) - these are also very useful, for example under Errand you could have North, South, East, West. Etc. Or for people tags, you can group them under an umbrella "Team C" tag etc.
michelle1987 post on 09/20/2013 16:48#3

PRO

@Folke @bhkiv

Hello,

We have the plan to implement the "Responsibility of Area" feature. As for nest projects, we now have Goal->Project->Task ->Suntask, four hierarchies and temporarily, we have no plan to implement it, but will consider it in the future.

Thanks for your feedback and support.
Folke post on 09/20/2013 22:48#5

PRO

Actually, it would seem much simpler to have just two different building elements, just task and project. Why four? It is more complicated to have four different things, all with different characteristics and different rules.

If you could put projects within projects within projects within projects, etc ... (and order things manually within each project) ... then you could use these "projects" in any way you please - as goals, as area folders, as programmes, as projects, as subprojects, subsubprojects etc .... and then always have regular tasks at the very bottom. No subtasks would be needed, because you would just use regular tasks within a regular project and put that project were you want, and build your hierarchies however flat or deep you want.

But I appreciate all your great efforts .-)
And I am excited to see the next release. Best of luck :-)
michelle1987 post on 09/21/2013 02:47#6

PRO

@Folke

Thank you for sharing your ideas.

We will take it into account in the future improvement.