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/)]

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/)]

[devesh]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

     http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.
------------------------------------------------------------------------
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.



Emacs  : GNU Emacs 24.3.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.8.8)
 of 2014-06-10 on worker1.bsys.centos.org
Package: Org-mode version 8.2.10 (8.2.10-23-g1ec416-elpa @ /home/devesh/.emacs.d/elpa/org-20141208/)

current state:
==============
(setq
 org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe
		      org-babel-hide-result-toggle-maybe org-babel-header-arg-expand)
 org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook)
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-confirm-shell-link-function 'yes-or-no-p
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-agenda-dim-blocked-tasks 'invisible
 org-mode-hook '(#[nil "\300\301\302\303\304$\207"
		   [org-add-hook change-major-mode-hook org-show-block-all append local] 5]
		 #[nil "\300\301\302\303\304$\207"
		   [org-add-hook change-major-mode-hook org-babel-show-result-all append local] 5]
		 org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-stuck-projects '("+project" ("NEXT") nil "")
 org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe)
 org-enforce-todo-dependencies t
 org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
		  org-cycle-hide-inline-tasks org-cycle-show-empty-lines
		  org-optimize-window-after-visibility-change)
 org-tags-exclude-from-inheritance '("project")
 org-todo-keywords '((sequence "TODO(t!)" "WAITING(w!)" "NEXT(n!)" "INPROGRESS(i!)" "DONE(d!)"))
 org-confirm-elisp-link-function 'yes-or-no-p
 org-metadown-hook '(org-babel-pop-to-session-maybe)
 org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent)
 org-agenda-files '("~/org/test.org")
 org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
 )

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]

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