I’ve written a small custom bit of JS/CSS to make properties of TODOs collapsible/expandable:
You can also query all TODOs by their custom property and display a table:
All code can be found in this gist:
Let me know what you think!
That’s very very pretty 
.
I’ve been working towards something like that for a while now and never had a chance to get my teeth into it. (I have negligible experience with JavaScript which is a bit of a hurdle).
I’ve often thought that what I’m missing from Logseq is the ability to organise the jobs I have to do in a way that is intuitive and that certainly is.
May I ask how you handle dependent tasks. I’ve been doing it with a ‘waiting’ property having that property reference either another job or a person (such as my boss).
I’m just finishing some work using Metaloid’s ‘kits’ to work with that system a bit smoother.
I’m completely new to Logseq and didn’t even know you can create dependent tasks. Do you have an example of what this looks like in Markdown? Is it just having a parent task with sub-tasks? If so it should already work:
But if you link it in a property like so:
TODO Deploy new feature
priority:: 2
status:: blocked
waiting:: [[TODO Fix critical bug]]
assignee:: [[John Doe]]
dependency-type:: technical
it would just render the reference:
What you could do is use block references:
- TODO Main project task
priority:: 3
subtasks:: ((683f1cbe-0637-484e-8b84-2fc30271369d)) ((683f1cc0-284c-4b80-a2e3-5bde4d900c47))
- TODO Subtask 1
priority:: 3
- TODO Subtask 2
priority:: 1
But then the sub-tasks would not render a properties list within the main task properties.
Could be done, I think, but not sure how many levels or complete recursion makes sense for this.
Let me know if you have an example so I better understand your setup of dependent tasks.