“complete subtasks in order” is useful for some smaller, simpler projects. When you get to the larger and more complex stuff you need to handle some diverse types of scheduling constraints. “Forced Next” seems like a good way to handle some but not all types of scheduling constraints. In my opinion a more generalized answer is the dependency constraint handled by MLO. With this, you can set up a project where task b becomes active when task a is completed, tasks c and d both become active when task b is completed, task e becomes active when tasks c and d are both completed and also task x from some other project has been completed, and task f becomes active five days after task e is completed. All of this is currently available. Dependencies can only be created on the desktop but once created will be processed correctly on desktop or mobile.
This is more work because all of the simple tasks where M follows L which follows J have to be coded as simple but explicit dependencies. But once it’s set up it’s easy and powerful to use. One more bit of good news is that the really big and complex projects that need this often closely resemble the last big and complex project you ran, so you can create a template and then just create a new project from the template and it will come up with all the dependencies predefined. -Dwight From: [email protected] [mailto:[email protected]] On Behalf Of John Smith Sent: Thursday, November 27, 2014 5:17 PM To: [email protected] Subject: [MLO] Feature Request: We need a 'Forced' Next Action to allow more than one Next Action per large project Hello In the app I have just left (the rather good GTDNext), they have an incredibly useful feature called "Forced Next". The idea here is that particularly on larger projects you do not want to be overwhelmed by seeing too many Next Actions on the screen at once. However although you want to "complete subtasks in order" or at least you want to complete MOST of them in order, in reality life is seldom that simple and sometimes you want to select one or two additional tasks to appear in the Next Action list. This means that for a larger project with a larger number of items, you are not constrained to just having the *one* Next Action, nor are you overwhelmed with seeing the whole queue of future Next Actions all at once. I have posted my request here: https://mlo.uservoice.com/forums/9235-general/suggestions/6777433--forced-next-action-so-that-we-have-have-more-tha Anyone else want to vote for it? J P.S. I am a newbie to MLO so I am hoping that I have done the correct thing. -- 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 http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/0c7ea01b-815a-4039-bcba-9c486eb0cdb9%40googlegroups.com <https://groups.google.com/d/msgid/mylifeorganized/0c7ea01b-815a-4039-bcba-9c486eb0cdb9%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 http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/00d701d00b73%24ff5e7770%24fe1b6650%24%40dwightarthur.us. For more options, visit https://groups.google.com/d/optout.
