Hi, this is how it works in my productivity system. First, I think MLO is meant to have unlimited subtask hierarchy and the flexibility it provides. I can see right away that I don't like Asana's approach, where you have a subtasks *inside* a task, without further split possible. How it works in my MLO:
- I mark "Complete subtasks in order". This way I see only the first subtask for each group. - I mark all tasks, which contain subtasks as Projects. This way I see the project name in square brackets for every subtask in my to-do list. - I can adjust the first subtask's name accordingly, or even group them, to flexibly set up what I want to see in the to-do list. - In a complex project, a Task Dependencies can also be used, if "Complete subtasks in order" is too complex to set up. That's basically it. I'm not using "Hide branch in to-do list" for actionable tasks at all, only for reference items. I manage everything with task hierarchies and dependencies, if needed. On Wednesday, May 16, 2018 at 9:16:06 AM UTC+3, Damo Skees wrote: > > I use MLO for home and work, and we use Asana for work. Asana still > misses many features that MLO has, hence I'm not using it for home yet, but > it has one great recent feature that I really find useful. > > These are 'subtasks' (link <https://asana.com/guide/help/tasks/subtasks>). > They're very simple - just a checklist that you can have under a task. > > However - I do find this extraordinarily useful. The fact is, for my work, > I tend to structure my day in terms of 3-4 major tasks for the day. Now, I > may have a list of subtasks within one or more of these, which I drew up > while I was planning the task, but I don't want all those to be displayed > in a flat todo list, since it becomes noisy and hard to maintain a > high-level view. I'm going to think in terms of the high level task, view > those, and then when I'm ready to dive into one, I'll focus on the > checklist of subtasks within that. Asana does give a quite clean approach > to that. > > Now, the thing is, MLO is (of course) capable of the same view - which is > *Hide > Branch in ToDo*. Hence if I have a major task, I can create several > subtasks. I then check *Hide Branch in ToDo*, and it should hide the > subtasks so I can still see the wood for the trees. > > The trouble is, of course, that *Hide Branch in ToDo* *hides the major > task itself*. Hence I'm unaware of the major task as well as the subtasks. > > To get the same effect, I would have to do this: > > Prepare for Morning > \-- *These are my hidden subtasks* [Hide Branch in ToDo checked here] > \--- Load dishwasher > Lock doors > Set alarm > Turn out lights > > Manually adding this 'intermediate' *<These are my hidden subtasks>* > entry just to be able to hide them properly is a pain, and seems wrong. > > So what I was wondering is, are people finding this feature useful as it > is, with the major/parent task itself hidden, or would it be more useful to > have only the subtasks hidden? How do people use this feature? > > I do see i'm not the only one - there's a uservoice requesting this here > <https://mlo.uservoice.com/forums/9235-general/suggestions/4445486-change-hide-branch-in-todo-to-hide-children-in> > > - but there are few votes for it. > > Many thanks, > > > Damo > > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/42a1b2fb-131e-48be-89ab-0e2d9c3c6128%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
