Re: Bug: weird interplay between enforce dependencies, stuck projects and previous subtree [8.2.10 (8.2.10-23-g1ec416-elpa @ /home/devesh/.emacs.d/elpa/org-20141208/)]

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Hello,

devesh <right.ho@gmail.com> writes:

> When org-enforce-todo-dependencies is t, stuck projects definition is
> simply '("+project" ("NEXT") nil ""), and org mode file looks like :
>
> * A                                     :project:
>   :PROPERTIES:
>   :ORDERED:  t
>   :END:
> ** TODO B
> * C                          :project:
> ** TODO D
>
> Both A and C appear as stuck projects, which is expected behaviour.
>
> But if A itself becomes TODO, like below:
>
> * TODO A                                     :project:
>   :PROPERTIES:
>   :ORDERED:  t
>   :END:
> ** TODO B
> * C                          :project:
> ** TODO D
>
> Not only A vanishes from stuck projects, but C also vanishes. No stuck
> projects are shown for the above file.
>
> One subtree should not affect the next, even if first is ordered and
> org-enforce-todo-dependencies is t.

Could you update Org to latest ELPA version and test it again? It may
have been fixed since then.


Regards,

-- 
Nicolas Goaziou