A: Hi aslkdfj,

Thank you so much for your wonderful feedback on WorkZappy! We're thrilled to hear you're finding it fast, aesthetically pleasing, and intuitive. We appreciate you taking the time to share your initial thoughts.

Regarding your crucial requirement for dependencies, especially for subtasks, let me clarify our current capabilities:

1. Current Dependency Capabilities:

Top-Level Task Dependencies: Yes, WorkZappy absolutely supports dependencies between work items (which can be your top-level tasks). We offer several types, including "Blocking / Blocked by," "Parent / Child," "Duplicates," and more. The "Blocking / Blocked by" relationship allows you to define that one work item must be completed before another can proceed.

You can find detailed information on this here: https://guide.workzappy.com/project/new-work/dependency
Achieving Dependencies for Components of a Task (Subtask-like Dependencies):

It's important to clarify that our built-in "Subtask" feature (detailed here: https://guide.workzappy.com/project/new-work/subtasks) is designed for very simple, lightweight checklist items that are directly part of a parent work item. These specific "Subtask" entities do not have their own independent dependency settings or relationships between each other.
However, to achieve the kind of dependency relationships you need for more detailed components of a larger task (effectively creating dependent sub-components or what you might consider subtask-to-subtask dependency), you would structure these components as full "Child Work Items" under a "Parent Work Item."

These "Child Work Items" can have dependencies set up between them. For example, you can use the "Blocking / Blocked by" dependency (from our general dependency types) to make "Child Item A" (which functions as one of your detailed sub-tasks) block "Child Item B" (another detailed sub-task), especially if they are both children of the same parent work item.

This parent-child structure, and any dependencies established between these child work items, are clearly visible and manageable in our Hierarchical Tree View: https://guide.workzappy.com/project/work-table/hierarchical-tree-view. This view allows you to see the full breakdown and relationships within your project.

2. Roadmap/Priority:

Given the above, the functionality to establish dependencies between top-level tasks, and also between "Child Work Items" (which serve as your more complex, dependent sub-components), is currently available. The "Blocking / Blocked by" dependency can be applied to any work item, including those designated as children.
We believe this approach of using Parent/Child work items and applying standard dependencies between the children offers the robust dependency management you're looking for.

We encourage you to try structuring your project this way: create a parent work item, then add separate child work items for its sub-components, and finally apply the "Blocking / Blocked by" dependencies between these child items as needed.