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: Mon, 20 Jun 2011 19:37:29 -0400 Message-ID: <87fwn4f51i.fsf@norang.ca> References: <20110620155011.5fe773ea@hsdev.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:54683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYo2J-0002K4-38 for emacs-orgmode@gnu.org; Mon, 20 Jun 2011 19:37:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QYo2H-0007SF-70 for emacs-orgmode@gnu.org; Mon, 20 Jun 2011 19:37:42 -0400 Received: from mho-04-ewr.mailhop.org ([204.13.248.74]:57167 helo=mho-02-ewr.mailhop.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYo2G-0007RD-RU for emacs-orgmode@gnu.org; Mon, 20 Jun 2011 19:37:40 -0400 In-Reply-To: <20110620155011.5fe773ea@hsdev.com> (Marcel van der Boom's message of "Mon, 20 Jun 2011 15:50:11 +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: > Hi all, > > I've run into an annoyance wrt the :ORDERED: property and the blocking > of tasks due to it. > > Here is the minimal usecase: > > --- > * TODO Project like header, containing subtasks > :PROPERTIES: > :ORDERED: t > :END: > ** TODO This item is the first to be done in the project > This one is not blocked, as I expect. ok > ** TODO Next task with subtasks > This is blocked by the sibling above, which is what I expect ok > *** TODO Subtask of a blocked sibling. > This seems to be blocked and I can't understand why. Marking it DONE would not mark the parent > done (neither explicit nor implicit). Why is it blocked then? Bug? This is blocked until you mark the first level 2 TASK as DONE. The entire subtree is blocked by the previous incomplete task. > *** TODO Second item in the blocked > This is also blocked, which could be right, because the parent > project has an ordered property and the sibling above is not yet > complete. > --- > > 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. -Bernt > > The above minimal case is easy, but it's far from trivial to see why > tasks in projects are blocked if the project is longer and has more > outline levels. > > My expectation of the ordered property would be that it only acted > one-level deep, regarded from a 'block-or-not' standpoint. > > Thoughts? -- Bernt