From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: Subtasks are blocked in todo-items of ordered projects. Bug? Date: Tue, 21 Jun 2011 07:30:56 -0400 Message-ID: <8739j3fmkv.fsf@norang.ca> References: <20110620155011.5fe773ea@hsdev.com> <87fwn4f51i.fsf@norang.ca> <20110621105945.5ecfd641@hsdev.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:36435) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYzAg-00046T-2U for emacs-orgmode@gnu.org; Tue, 21 Jun 2011 07:31:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QYzAa-0004NL-Rq for emacs-orgmode@gnu.org; Tue, 21 Jun 2011 07:31:05 -0400 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:61076 helo=mho-01-ewr.mailhop.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYzAa-0004N2-EB for emacs-orgmode@gnu.org; Tue, 21 Jun 2011 07:31:00 -0400 In-Reply-To: <20110621105945.5ecfd641@hsdev.com> (Marcel van der Boom's message of "Tue, 21 Jun 2011 10:59:45 +0200") 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: Marcel van der Boom Cc: emacs-orgmode@gnu.org Marcel van der Boom writes: > On ma 20-jun-2011 19:37 > Bernt Hansen wrote: > >>> Should the first task in a subproject of a project >>> having the ':ORDERED:' property set to true be blocked from marking >>> 'DONE'? If so, why? >> >> I think the answer is yes it should be blocked because the entire tree >> is blocked - the previous task needs to be DONE first. When the >> subtree is unblocked you can then complete the first task in the >> subtree. > > Ok, to get the behaviour I want, I could remove the 'TODO' keyword > from the subproject. > > That will allow me to work on the subitems in parallel. Obvious > disadvantage is that the subproject as such can only have a > 'count' or 'percentage' but not a 'state' and thus cannot be tracked > anymore. > > Any other suggestions for a way to work on subitems in parallel with the > 'main tasks'? I'll spent some time digging if the wanted > behaviour could be formulated as an option to set without disturbing > the default behaviour. You can work on things in parallel - you just can't mark them as completed. I clock in time on tasks I work on which changes TODO to STARTED and there is no restriction (that I'm aware of) on doing this. You can also force the task state to DONE with a triple prefix (C-u C-u C-u C-c C-t d) which will ignore the blocking rules for this state change. HTH, -- Bernt