>From a GTD point of view, using Tags to control a task's "List" (i.e its actionable status such as @Someday @Later @Waiting etc) is unacceptable for a combination of reasons
1. I want to use Tags to control Context and if one starts using Tags to control both Context *and* List, things start to get very messy! e.g. When one is trying to view all your Tasks grouped by Contexts, then then Tags such as @Someday @Later @Waiting immediately start cluttering up your views. 2. It's also rather a pain to change the actionable status of and entire project as you need to select all the tasks at once within a project before making the change 3. Obviously it's also possible to have any given Task appear in multiple GTD lists at once (e.g. @Someday @Later @Waiting), so moving between GTD Lists is stupidly clumsy. 4. When view tasks and wanting to change between different Contexts, the Tag names are also cluttered up with tag names like @Someday Sadly Flags don't work well either for Controlling GTD status list either because (unlike Tags) they don't inherit their values from parent tasks when being created. The long and short of it is that MLO needs separate fields for the "Status" and Context of a task, and when the user tries to do these sort of workarounds, there are always various unintended consequences. With thanks J PS I have had a quick look at the Windows MLO Version 5 beta video https://www.youtube.com/watch?v=ZvwcHwF0yXs and from what I can see there is no sign of any improvement in this problem. :^( On Saturday, December 30, 2017 at 2:29:20 PM UTC, Elizabeth Lindsay wrote: > > I see a couple of other folks have replied prior to be seeing this, but I > felt the need to chime in as well. I've been using MLO for many years, am a > BETA tester, and follow GTD. From my perspective: > > 1. Only a project needs a status, and MLO has that. > 2. All tasks availability can be managed either: > 1. Using an "@Someday" context to show it is not for now (and I > have MLO automatically format them in a color that appears greyed out) > 2. Linked to another tasks that has to be done first and therefore > this particular task is not active > 3. The child of another tasks, therefore this one has to be done > first and not the parent > 4. In a list of tasks that are checked to be "completed in order" > 5. Adding a start date to not show things prior to a particular > date/time > > In all those cases, my list of active tasks is showing me what is > available to me. Then I use contexts to provide my GTD contexts. > > As David replied, I too manage hundreds plus of tasks on Android and > Windows and follow the GTD system. > > I've even added my own custom icons to make it quick for my eyes to see > various types of activities. > > I wish you all the best! > Elizabeth > > On Friday, December 29, 2017 at 7:15:12 AM UTC-6, John . Smith wrote: >> >> >> In the end, having tried MLO in about 10 different ways, and having spent >> countless hours fiddling and configuring MLO, I eventually found MLO to be >> unusable for GTD if you have fairly large numbers of tasks (e.g. 200+). >> >> In particular the lack of a field that could be used as a Status field >> (that unlike flags would 'inherit' sensibly) was a deal breaker. It was a >> huge shame because MLO is astonishingly powerful in so many ways... but >> there you go. >> >>> >>>>> -- 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 mylifeorganized+unsubscr...@googlegroups.com. To post to this group, send email to mylifeorganized@googlegroups.com. 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/30c60e53-ada6-40f5-9766-7ba1475d7063%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
