Hi Dwight Now I'm with you. What you describe about Task4 only appearing after Task2 and Task3 have been completed is true in the 'no hierarchy' view but not in the 'with hierarchy' view, yes?! Fwiw, currently I seem to use both!
Fwiw my ForcedNext action flag is seems v useful so far :) Fwiw, it does involve quite complex Advanced filters though. The problem is that unlike Show Actions:Active, just setting ActiveAction=true in advanced filters doesn't seem to pay attention to either a task's Start Date nor hidden-in-to-do status, so this has to be done manually. So to recap, if I am using "complete subtasks in order" in order to have a Flag for my desired "ForcedNext" functionality whereby I can have additional tasks of my own manual choosing appear I in my customised version of 'active tasks' view, I now have an advanced filter that looks like this: (not(HideInToDo)) AND ((StartDateTime on or before now) OR (StartDateTime does not exist)) AND ((ActiveAction) OR (Flag=~ForcedNext)) Seems to work so far... :^) One slight problem is that "complete subtasks in order" only seems to filter for ONE layer of hierarchy. i.e. It filters out children but not grandchildren deriving from those children's children. i.e. suppose you had a structure of data as follows: Project A > Task1 > > Task1.1 > > > Task1.1.1 > > > Task1.1.2 > > > Task1.1.3 > > > Task1.1.4 > > > Task1.1.5 > > Task1.2 > > > Task2.1.1 > > > Task2.1.2 > > > Task2.1.3 > > Task1.3 > Task2 > Task3 > Task4 If you make Project A set to be ["Complete subtasks in order"], then in Active tasks with hierarchy on view, what you would now see would be ALL of the following: Project > Task1 > > Task1.1 > > > Task1.1.1 > > > Task1.1.2 > > > Task1.1.3 > > > Task1.1.4 > > > Task1.1.5 > > Task1.2 > > > Task2.1.1 > > > Task2.1.2 > > > Task2.1.3 > > Task1.3 i.e. Only Task2, Task3 and Task4 are actually hidden by using "Complete subtasks in order". ASIDE: Of course only the following would be visible in Plain List view: Task1.1.1 Task1.1.2 Task1.1.3 Task1.1.4 Task1.1.5 Task2.1.1 Task2.1.2 Task2.1.3 Task1.3 Whereas my real point here is that if I use the filter "Show Actions:NextActions", the filtering does (for better or worse) go right to the END of the hierarchy and all one would see is this: Project A > Task1 > > Task1.1 > > > Task1.1.1 Or in list view (without either prefix or postfix) one would just see: Task1.1.1 [ASIDE: I find it surprising that one doesn't need to even make 'Project A' become an MLO Project for this to work - it just sort of assumes that the first action in the tree *is* part of a project.] However if of course you want to have a sub-project elsewhere in the hierarchy, you would just need to set it as a MLO project. e.g. In the structure below, suppose I wanted Task3 to be a sub-project Project A > Task1 > > Task1.1 > > > Task1.1.1 > > > Task1.1.2 > > > Task1.1.3 > > > Task1.1.4 > > > Task1.1.5 > > Task1.2 > > > Task2.1.1 > > > Task2.1.2 > > > Task2.1.3 > > Task1.3 > Task2 > Task3 > > Task3.1 > > > Task3.1.1 > > > Task3.1.2 > > > Task3.1.3 > > > Task3.1.4 > > > Task3.1.5 > > Task1.2 > Task4 If Task3 is set as an MLO project what would be visible in Next Actions with hierarchy on would be the following: Project A > Task1 > > Task1.1 > > > Task1.1.1 > Task3 > > Task3.1 > > > Task3.1.1 Or in plain list view the Next Actions would simply be: Task1.1.1 Task3.1.1 So is there any way of making "Complete subtasks in order" apply to SUB-subtasks, as it's a slight pain to have to mark my sub-tasks with their own "Complete subtasks in order" in order to stop unwanted grand-children from appearing!? This was the reason I abandoned "Complete subtasks in order" originally - for larger, more complex projects you have to keep applying it in multiple places in order to stop grandchildren from flooding the view! J On Thursday, December 15, 2016 at 12:34:22 PM UTC, Dwight wrote: > > > > > On December 15, 2016 12:53:03 AM Dwight <m...@dwightarthur.us > <javascript:>> wrote: > > > Hi, John. I mentioned that the more efficient form of the project > > "appears to the human eye to be out of order" and you clearly have a > > strong case of this but I promise you, the order is correct. Type this > > in and run it, you will see what I mean. After task 1 is done the next > > one to appear is not 4, it's 2 and 3 together. task 4 cannot appear > > because it is inactive, due to having uncompleted subtasks. Only when > > the subtasks are completed can the parent appear. > > > > Your "moreover" point is valid though I would say it differently. > > Setting up the tasks in this form means that checking off task 4 means > > that you have completed (or cancelled) tasks 2, 3, and 4. If you have > > completed task 4 out of order but still need 2 and 3, you would have to > > re-order the tasks. > > > > Anyhow, since you are a "thinking in shapes" person you should probably > > avoid this, as well as any sort of reverse polish notation. > > > > -Dwight > -- 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/142fdc86-d9be-4d83-857d-c10255b3030f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
