Hierarchical tasks with queryable subtasks (checkboxes or child tasks)
I’m using Capacities’ new Task object extensively and I’d like to model subtasks in a way that is both:
- Hierarchical – subtasks are tasks that belong under another task (not just under a project or other object type), and
- Queryable – I can get a global overview of all subtasks across my space.
Right now there is no explicit subtask concept for Tasks. I can add checkboxes inside a Task and treat them as subtasks, but I cannot query all checkbox items across all Tasks/objects.
So I can’t get a global “all subtasks” view.
I also cannot add custom properties to the Task object , so I can’t model a clean parent/child relationship between Tasks (e.g. Parent task, Subtasks properties).
Because of this, my task list “explodes” if I try to model every subtask as a separate Task object, and I still don’t get a proper hierarchical view. A flat task list with dozens of items is practically unusable.
What I’d love to have.
I see two possible directions (either would help a lot):
- First‑class hierarchical Tasks
- Allow Tasks to have other Tasks as subtasks (parent/child relationship).
- Make this relationship visible in the UI (expand/collapse subtasks under a parent).
- Make it queryable (e.g. filter for all subtasks of a given parent, or all open subtasks).
- Global querying of checkbox subtasks. If subtasks are meant to be checkboxes inside Tasks, provide:
- A way to query all checkbox items across my space.
- Filters like: “only unchecked”, “only those inside Tasks”, “only those inside Tasks with status X”, etc.
This would let me keep subtasks lightweight (checkboxes) but still have a global overview.
Either approach would solve the core problem: I want to use subtasks without losing the ability to see and manage them across my whole space.
0 Comments
Sign in to comment
No comments yet. Be the first to share your thoughts!
