From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viktor Rosenfeld Subject: Re: What do you use to identify projects (in the GTD sense) Date: Mon, 12 Dec 2011 19:29:55 +0100 Message-ID: <20111212182955.GB46849@kenny.fritz.box> References: <87ty7ge2p1.fsf@norang.ca> <20111211164948.GA1082@kenny.fritz.box> <87wra2eorn.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([140.186.70.92]:55849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RaAdV-0000Pw-9S for emacs-orgmode@gnu.org; Mon, 12 Dec 2011 13:30:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RaAdU-0006D4-3v for emacs-orgmode@gnu.org; Mon, 12 Dec 2011 13:30:01 -0500 Received: from mail-bw0-f41.google.com ([209.85.214.41]:48527) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RaAdT-0006Cz-Qg for emacs-orgmode@gnu.org; Mon, 12 Dec 2011 13:30:00 -0500 Received: by bkbzt12 with SMTP id zt12so6700851bkb.0 for ; Mon, 12 Dec 2011 10:29:58 -0800 (PST) Content-Disposition: inline In-Reply-To: <87wra2eorn.fsf@norang.ca> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bernt Hansen Cc: emacs-orgmode@gnu.org Hi Bernt, sorry, I wasn't more specific. My problem is with projects that consist of subprojects and simple tasks. Consider the following scenario: * TODO Project ** TODO Subproject A *** NEXT Task A1 *** TODO Task A2 ** NEXT Task B ** TODO Task C ** TODO ... Task B and C have to be done in order. However, Subproject A is somewhat independent and can be done in parallel, while working on Task B and C. When I mark Task B as DONE, the Project is still unstuck because of the a NEXT task in Subproject A. Meaning that I never get to schedule Task C or any following tasks until I'm done with Subproject A. One solution to this problem would be to trigger a state change in Task C automatically when Task B is done. But I'm afraid that is too much setup and also not flexible enough. Often, when I consider a stuck project I schedule next actions that I haven't thought of before or even put the project on a someday list. Another solution would be to implement a stale projects list, i.e. a list of projects that have defined next actions, but haven't seen any work in the last X days. Cheers, Viktor PS: Your org-mode site is generally the bomb! Bernt Hansen wrote: > Viktor Rosenfeld writes: > > > I use Bernt's approach with a few modifications. Basically I don't use > > subprojects. I think Bernt's handling of subprojects is broken, because > > a NEXT keyword burried in a subproject keeps the entire project off the > > stuck projects lists. (Please correct me if I'm wrong.) > > It's possible it's broken :) but subprojects are considered separately > for the stuck project list. It is true that if any subproject has a > NEXT task then the overall project is not stuck (but doesn't that makes > sense?) > > * TODO Project > ** TODO SubProject A > *** NEXT Task One > ** TODO SubProject B > *** TODO Task Two > > In the above layout Project is not stuck (it has Task One as a NEXT > task) but SubProject B is stuck (it has no next task and shows up on the > stuck project list) > > Also as soon as Task One is DONE than both SubProject A and Project are > both stuck until a new NEXT task is identified (or they are in turn > marked DONE) > > Regards, > Bernt >