Hello Jon, If you're a user of the classic "GTD" method, then you should avoid setting any dates other than hard deadline dates (the ones where "after this date, the task is invalid because it's too late"). Treating due dates as absolute means that they should always be set ahead of undated items - that's the theory, anyway. If that doesn't work for you, then you should be able to set up custom filtering and sorting in a view so that items are only sorted by importance, ignoring the due date. It's probably best to start with the basic To-Do list view and then set up your own custom filter from scratch, with the filtering and grouping criteria you want.
On Thursday, 9 December 2021 at 15:15:45 UTC Jon R wrote: > I am a new user but see there is an option to sort a branch under the > context menu 'advanced - sort subtasks'. I guess this was implemented since > OP's ancient question! > > I confess that MLO is very powerful/configurable, and hence complex - I am > still learning! So all I can report is my method: > > I prefer the outliner to sort top level parents according to importance > etc, while the tasks (children aka leaves) within each parent are manually > set up in a sequence (no need for priority fields etc). MLO knows to > present the first/next incomplete one in the 'todo' list. > > But if a complex project has multiple parallel tasks I can see that > sorting them per OP's question is needed (or maybe a filter?) to sort the > wood from the trees. Warning - I have not tested this and see the menu says > 'this cannot be undone' - I would be afraid of borking the entire tree by > mistake. "With great power... etc". > > *My bolt-on question* (perhaps deserves a new thread...) is that I notice > that however I tweak the settings, the todo list always bunches dated items > right at the top (including recurring tasks), and non-dated below, very > rarely putting non-dated items among the dated ones. > > This is awkward for me bc I want to fulfill the opening paragraph of the > MLO introduction - i.e. to prioritise high value projects among the regular > fluff of life and work. > > I feel that setting a 'date' imposes a heavy implication of 'must', > whereas this is not true at all. E.g. if I set a date to remind me to do a > recurring task, it might be mundane like 'take clothes for pressing'. The > settings for priority etc don't seem to have enough influence over the due > date. > > Does anyone else feel this way? > > > On Saturday, December 4, 2021 at 5:20:44 PM UTC Stéph wrote: > >> I'm not sure I fully agree with you. I think sorting should be as you >> describe if you are viewing tasks in a flat list. However, if you're >> looking at tasks within their hierarchy, then I don't think the sorting >> should change the outline hierarchy, duplicating branches and tasks. If >> you're choosing to view tasks within their outline hierarchy, then it would >> be quite confusing to override that outline with the sort criteria. (If >> I've misunderstood what you're suggesting, then my apologies - I'll blame >> my confusion down to my current bout of COVID-19). >> >> Stéphane >> >> On Saturday, 4 December 2021 at 09:41:49 UTC [email protected] wrote: >> >>> Hi, have we made any progress since 2013 regarding this enhancement? >>> Hierarchy should be used simply to put tasks in context, not to get in the >>> way of sorting. Sorting should consistently be applied to main filters >>> matches only, even if that means seeing the same hierarchy multiple times >>> in this view. We already have the main outline (all tasks) for neat >>> structures where items appear once. It feels very out of place in the >>> context of a view since it conflicts with the primary function (which is to >>> tackles individual tasks, regardless of location, in the chosen order). >>> Thanks! I don't know how active MLO has been these last days... It's >>> definitely not the most famous app for GTD but the team has done an >>> excellent job so far. It would be a shame to leave it there. >>> >>> On Wednesday, October 23, 2013 at 5:39:25 AM UTC+2 Dwight Arthur wrote: >>> >>>> Sorry, no. >>>> For views that show a hierarchy, any defined sort is applied to the >>>> root (parent) level and not to the leaf (child) level. Sometimes this >>>> leads >>>> to clearly undesirable results, such as when a particular view shows a >>>> single branch of the hierarchy, so that the level where the sort is >>>> applied >>>> contains only a single item. At some point there was a discussion in the >>>> forum suggesting that the defined sort should be applied at every level to >>>> items that shared a common parent. But this suggestion was never >>>> formalized >>>> as an enhancement request, so it's unlikely that it will be implemented >>>> any >>>> time soon. >>>> -Dwight >>>> >>>> On Monday, October 21, 2013 11:49:06 AM UTC-4, 元亨大吉 wrote: >>>>> >>>>> ... Is it possible to sort the children tasks within a parent project >>>>> buy due date? >>>>> >>>>> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/1da93a01-a0c4-4eef-8f97-0656df7fdeacn%40googlegroups.com.
