+ Add Question

Parent projects and sub projects

AB

Hi, I really like todoist but there's one thing that bugs me. I have a project called "Next Actions", and in GTD style this contains sub projects called "@home", "@calls", etc. which are indented. Each of these sub projects has its own tasks/subtasks.

When the disclosure arrow next to the "Next Actions" project is pointing to the right and only this project is showing, the number next to it indicates the number of TASKS contained in all of the subprojects. I think it would be much better if this number showed the number of sub projects, not the number of tasks. Is there any way to achieve this?

Also, when I click on "Next Actions" and all sub projects are displayed on the right hand side, why is the main parent project (Next Actions in this case) shown as the same size and font as the sub projects? Shouldn't this be larger to indicate that it's a header which contains all the sub projects? Also, why does this header have the option to "add task" in this view? Is there any way to turn this off?

Thanks for your help.

All responses

David Trey staff
Replied on Jan 05, 2014 - 15:09

Hello Anthony,

Unfortunately, that's not possible. These counters always show the number of tasks within a project and if you collapse a project structure, the numbers get added to show you how many tasks you have in this structure.

Regarding your second question - when you click on the name of the parent project, then you will see all of the projects in this structure listed with tasks below them. On the right, the project structure itself is not shown, only a list of tasks below the projects' names. It's not possible to show the structure without the name of one or multiple projects.


Best regards,
David

AB
Anthony Bee premium
Replied on Jan 05, 2014 - 16:57

Hi David, thank you for your reply.

I think my problem stems from the fact that my "Next Actions" parent project, is actually not a project at all. At least, not in the way I'd like to use it. my "Next Actions" list is just a place-holder, which itself holds other place-holders (sub-projects in todoist speak) like @home, etc., which finally hold tasks. I'd never need or want to add a task to a place-holder, since it's only the deepest sub-projects which contain the tasks.

It's possibly just a conceptual difference, in the sense that todoist seems to assume by default that every list is a project. In the GTD literature "Next Action" lists are simply stand-alone lists containing single tasks.

This makes using todoist for GTD a little confusing, since, for example, in my list of projects on the lhs, I have a project called "Projects" :)

David Trey staff
Replied on Jan 06, 2014 - 06:40

Anthony,

In that case, you can use labels for next actions and projects for something else (context?). To do so, click on a task and type @next within its name - this will create a label and if you click on this label or type @next within the search bar, you'll see a label-based list.

This way you could use projects for different purposes and labels for others. Try it out and see if it works out for you :)


Best regards,
David

AB
Anthony Bee premium
Replied on Jan 06, 2014 - 10:25

David,

Thanks for the suggestion, I'll try that and see how it works out. The problem I foresee is that these labelled tasks are then left in the "inbox". In the GTD philosophy the inbox is simply a repository for unprocessed 'stuff', and should be cleared as often as possible. It doesn't contain next actions, which are single tasks arising from the process of thinking about and refining the ideas/thoughts/etc. in the inbox.

I suppose could create another project called 'labelled', in which to move these next actions. But I find this unsatisfactory, since 'labelled' or 'processed' is just a 'folder' or place holder, it's not a project.

It's not a huge deal or anything, and I don't think it will prevent me from renewing my premium subscription. But defining every item as either an "inbox" item, or as a project, seems to be somewhat at odds with the GTD philosophy (at least that espoused by David Allen).

Having said that, of course I'm aware that not everyone using todoist will want to apply this approach.

Anyway, I'll try using labels and see what happens. Thanks