This package is a proof of concept from this reddit thread:
https://www.reddit.com/r/emacs/comments/i9jv3l/orgedna_how_to_set_scheduled_todo_keyword_only/
Package heavily relies on org-ql package.
The usage example video demonstrating how it works with example.org.
To make a relation between tasks:
- Insert ID property to a parent task;
- Insert LINKED property with ID value of a parent to its children;
With this being done, a parent task will be blocked by its children as long as
there is at least one child somewhere in (org-agenda-files)
. You can list tasks
which are blocking parent task via org-linked-tasks/show-linked-tasks
interactive function.
When the last child is marked as done, the parent will be scheduled for today and todo state will set to NEXT.
Package at this stage is more in the proof of concept stage rather then finished idea. The functionality introduced by this package is too inflexible and doesn’t play well with other similar packages: org-depend or org-edna.
Since all linking is done through the org-id
, we possibly can live absolutely fine without this hard dependecy.
Action customisation is done through the elisp function. This is not an ideal design, since user may want to have varying behaviour for different headlines. May be introduce additional property that will understand org-edna
or org-depend
syntax?