UPDATE: It turns out that it's nothing to do with tasks having parents that are/are not Folders. Instead, it's about tasks having parents of any sort(!).
i.e. From what I can see, in the "Next Actions" view, for each task in the root directory (i.e. tasks which when in Hierarchy mode will align fully to the left), MLO will try to show just ONE task (i.e. the first task) that is not part of any Project. i.e. For any task that is in the root directory, when "Next Actions" view is switched on, MLO will attempt to find one child task, that is not part of a Project. Whereas in the "Active" view will, of course, show multiple child tasks. [ For completeness, MLO Projects work in Next Actions view exactly as you'd expect. i.e. For each Project, MLO attempts to show just one Task. And as noted, if a Project contains any Project within it (i.e. "sub-projects"), then MLO also attempts to show just one task for each of them too] OK I'm out of time.... but in summary: If you use do use any form of hierarchy or Folders within MLO, then getting "Next Action" view to show multiple stand-alone tasks appears to be impossible. J On Tuesday, January 23, 2018 at 1:12:10 PM UTC, John . Smith wrote: > > > > Thank you Dwight. > So although I find it rather confusing, it is roughly as I > remembered, then. > > But what is bemusing though is that from what I can see "Next Actions" is > treating anything flagged up as being a Folder in the same way as if it > were a Project. i.e. Only one child per FOLDER is ever visible. > > If so this seems to be an undocumented (and in my view unwelcome) feature. > > The User Guide ( > https://www.mylifeorganized.net/downloads/files/MyLifeOrganized%20User%27s%20Guide.pdf) > > reads as follows: > > > Page 47 Section 5.3.2 > > >>> > 1. Active > If Active is selected as the Action Filter then only Active tasks are > placed in the list first and then other > filters can be used to select tasks from this list. To be placed on the > list of Active actions, a task must > meet all criteria listed below: > 1) the task must not have subtasks or these subtasks should be completed > 2) the task must not have completed parent tasks > 3) the Start Date for the task is not set or Start Date is now or in the > past > 4) the task must not have the option Folder checked > 5) the task must not have the option Hide branch in To-Do List checked for > this task as well as for any of > its parents > 6) If one of the task's parents has the option Complete subtasks in order > checked, this task must have > all above siblings completed to be placed in the list. Or these siblings > can have Hide in To-Do option > set. > 7) If the task has dependency tasks these dependency tasks must have been > completed. > >>> > > > >>> > 3. Next Actions > If Next Actions is selected as the Action Filter then only Next Actions > are placed in the list first and then > other filters can be used to select tasks from this list. To be placed on > the list of Next Actions a task > should meet all the criteria listed for Active Actions. However only one > (first) active task for each project > is placed in the list. > Note: If there are Active Tasks without parent project then only first > task for each root task > is selected. > Note: If a project does not have open tasks then this project itself is > also placed on the list > as Next Action. > >>> > > Or am I missing something? > > J > > > > > > > > > > > On Monday, January 22, 2018 at 6:20:55 PM UTC, Dwight wrote: >> >> John, the last time you and I went through this, the result was that the >> Next Actions filter is available only as the global Action Filter and >> not as an advanced filter - the result of this is that if you have a >> view where any of the included items are there because of being a next >> action then *every* item included in the view must be a direct action. >> >> Long term solution: request an advanced filter for "Next Action". I >> believe that you have requested this. To the best of my knowledge there >> has been no movement towards implementing it. If you would like to >> influence this, the best method would be to become an active member of >> the beta test team and advocate for it there. >> >> Short term solution: as you noted, if a task needs to be included >> despite being not a next-action, make the task to be the only item in a >> subproject, by definition it will be a next-action. >> >> To answer your other question, A next actions view will include a task >> from a folder if it meets the definition of a next action. If there are >> no issues with start dates, dependencies, etc that should mean that the >> first task in the first subfolder is included. There are some parts of >> this that get intricate and I do not remember all of the rules, you >> should experiment. >> >> -Dwight >> >> On 1/22/2018 12:33 PM, John . Smith wrote: >> > PPS >> > Ah, now I remember. I am correct in thinking that the "Next Actions" >> > view doesn't any standalone actions (if they are inside a Folder) ?? >> > >> > J >> > >> > >> > >> > On Monday, January 22, 2018 at 5:19:16 PM UTC, John . Smith wrote: >> > >> > >> > PS A partial answer my requirement #2 (above) seems to be to use >> > Filter ==> General ==> "Show Next Actions", (which will show the >> > next 1 action in each Project) and for anything which I want to >> > manually flag up and force to appear, to make it into a sub-project >> > (e.g. by using Alt/J). If possible would prefer to use actual MLO >> > Flags because it would make reviewing slightly easier. >> > >> > J >> > >> > >> > >> > On Monday, January 22, 2018 at 5:11:29 PM UTC, John . Smith wrote: >> > >> > >> > Hello >> > >> > 1. Is it possible to create a view (i.e. workarea) in MLO >> > Windows that always shows the *next 3 tasks* within a project, >> > as well as showing any Active stand-alone tasks? >> > >> > 2. If not, is it possible to create a view that always shows >> the >> > next 1 task within a project, plus any tags that have been >> > manually flagged up in some way, as well as any Active >> > stand-alone tasks. >> > >> > From memory, I think the answer is that neither of these >> things >> > can be done in MLO, but I may have missed something(??). >> > >> > The background is that for my larger projects, I always want to >> > show more than one task at once on my to-do list. >> > >> > Many thanks >> > >> > J >> > >> > >> > >> > -- >> > 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] >> > <mailto:[email protected]>. >> > To post to this group, send email to [email protected] >> > <mailto:[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/f6e2f499-ec04-4b99-bce7-d8ea84d4ad4a%40googlegroups.com >> >> > < >> https://groups.google.com/d/msgid/mylifeorganized/f6e2f499-ec04-4b99-bce7-d8ea84d4ad4a%40googlegroups.com?utm_medium=email&utm_source=footer>. >> >> >> > For more options, visit https://groups.google.com/d/optout. >> > -- 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/ac43ef46-cc56-4c8b-bcea-e6f48244080f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
