Re dependencies - yes, I hear your. But setting up dependencies explicitly sounds sensible for larger projects (unless you do the entire planning elsewhere using dedicated PM software) however I IMHO, it is *way* too painful for small/medium sized projects.
e.g. Suppose I have a Project with 8 Actions. In GTD theory you need one Next Action for each project. But in reality I have 2 of them are good to go right now, (and both are urgent). I don't want to fiddle about with dependencies and I don't want to be overwhelmed by seeing all 8 actions either! I just want to see the two Next Actions. I mean count the keystrokes! Basically I want to bash all the Actions is a fast as possible into the correct project. TBH, even giving each of the Actions a context is *slightly* painful, but if I select all the ones with the same context at once I can enter them all in one go - NICE, btw! - but still a pain. [Aside: Is there any way for an action to *automatically* inherit the contexts for the Action above it in this list? I have spotted to fudge of creating a SUB-project and then Outdenting it. Yes not bad but still extra keystrokes] And then I have to tell the project that its setting is "Complete subtasks in order"... [deep sigh] Well this ought to be easy with the Alt P hotkey... but not so fast, first I must go and manually select the project we are in. So it's Left Arrow first and THEN Alt P. ==> [Again incrementally more keystokes!] And even though I know I'm going to want to set every project I ever have to "Complete subtasks in order", apparently there is no global default setting for this. (Is this really true, btw?) J On Saturday, November 29, 2014 1:30:07 AM UTC, Dwight Arthur wrote: > > “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] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *John Smith > *Sent:* Thursday, November 27, 2014 5:17 PM > *To:* [email protected] <javascript:> > *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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > 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/2f53c25d-4e74-45f8-80be-3075209b3d41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
