From mboxrd@z Thu Jan  1 00:00:00 1970
From: Allen Li <vianchielfaura@gmail.com>
Subject: Re: Bug: ordered property blocks grandchildren [9.1.3
 (9.1.3-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20171116/)]
Date: Mon, 27 Nov 2017 12:01:40 -0800
Message-ID: <CAJr1M6edxDR2fKjiMEV2jV1JjQr8JYwhnCScDdHT0h_+xhXntw@mail.gmail.com>
References: <CAJr1M6dtX6fXiT1ixupmHbxTSUZVZ6xK2knLXra9=qeyuFQc5A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45115)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vianchielfaura@gmail.com>) id 1eJPb5-0004zY-3w
	for emacs-orgmode@gnu.org; Mon, 27 Nov 2017 15:01:43 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vianchielfaura@gmail.com>) id 1eJPb4-0006c2-Ce
	for emacs-orgmode@gnu.org; Mon, 27 Nov 2017 15:01:43 -0500
Received: from mail-qk0-x233.google.com ([2607:f8b0:400d:c09::233]:39154)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <vianchielfaura@gmail.com>)
	id 1eJPb4-0006bm-8I
	for emacs-orgmode@gnu.org; Mon, 27 Nov 2017 15:01:42 -0500
Received: by mail-qk0-x233.google.com with SMTP id w125so34087925qkb.6
	for <emacs-orgmode@gnu.org>; Mon, 27 Nov 2017 12:01:42 -0800 (PST)
In-Reply-To: <CAJr1M6dtX6fXiT1ixupmHbxTSUZVZ6xK2knLXra9=qeyuFQc5A@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: emacs-orgmode@gnu.org

On Mon, Nov 20, 2017 at 5:18 PM, Allen Li <vianchielfaura@gmail.com> wrote:
> Create a file tmp.org with contents
>
>     * TODO parent
>       :PROPERTIES:
>       :ORDERED:  t
>       :END:
>     ** TODO child1
>     ** TODO child2
>     *** TODO grandchild1
>     *** TODO grandchild2
>
> 1. emacs -Q
> 2. M-: (setq org-enforce-todo-dependencies t) RET
> 3. C-x C-f tmp.org RET
> 4. Move point to grandchild2
> 5. C-c C-t
>
> user-error: TODO state change from TODO to DONE blocked (by "TODO child1"=
)
>
> The documentation emphasizes that ORDERED is not inherited.  The
> behavior that I would expect is that child1 blocks child2, but it should
> not block grandchild1 or grandchild2.
>
> However, I think the current behavior is also reasonable under some
> workflows.  I=E2=80=99m creating a bug to track opinions, if one behavior=
 is
> significantly more desired than the other, or if an option to control
> this behavior would be welcome.

There's an additional quirk to this behavior:

If the child is not a TODO heading, its grandchildren are not blocked


    * TODO parent
      :PROPERTIES:
      :ORDERED:  t
      :END:
    ** TODO child1
    ** child2
    *** TODO grandchild1
    *** TODO grandchild2

In this modified example, the grandchildren are not blocked, unlike
the original example.  Again I can see certain workflows relying on
this behavior, but the behavior isn't quite obvious.  The
documentation should probably be improved.  I'd also like to think
about the implications behind this behavior and any alternatives a
little more.