Feature: Subtasks

[kadel]

1. Overview
   The goal of this feature is to introduce "Subtasks" to our existing task management system. This API update will allow users to break down larger, complex tasks into smaller, actionable, and trackable child tasks (subtasks).

Subtasks will share the same core properties as standard tasks but will be hierarchically linked to a "Parent Task."

2. User Stories
   As a user, I want to create a subtask under an existing task so I can break my work into smaller chunks.

As a user, I want to view all subtasks associated with a specific parent task.

As a user, I want to easily delete a parent task and have all its subtasks automatically cleaned up (or specifically handled).

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 7:56 AM UTC · Completed 8:00 AM UTC

Commit: 77fa054 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Severity: Medium · Category: Feature

Design considerations:

• The existing API follows a RESTful pattern (/tasks, /tasks/:id). Subtask endpoints can follow the nested resource convention: POST /tasks/:id/subtasks and GET /tasks/:id/subtasks.
• The delete user story mentions cleanup "(or specifically handled)" — cascade delete (deleting all subtasks when a parent is deleted) is the simplest and most common approach for this pattern.
• Consider enforcing single-level nesting (no sub-subtasks) initially to keep the implementation simple.
• The existing GET /tasks endpoint should continue to work unchanged for backward compatibility.

Proposed test cases:

1. Create subtask under valid parent → 201, subtask has correct parentId
2. Create subtask under non-existent parent → 404
3. List subtasks of a parent → returns only that parent's subtasks
4. Delete parent task → all subtasks also deleted
5. Create subtask of a subtask → rejected (single-level nesting)
6. GET /tasks returns all tasks including subtasks (backward compat)

---

Labels: This is a new feature request for adding subtask hierarchy support to the task API.

---

Next steps:

• /fs-code — agent creates a PR to implement this issue
• /fs-code <your instruction> — agent implements with your specific guidance

[kadel]

/fs-code

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 8:01 AM UTC · Completed 8:05 AM UTC

Commit: 77fa054 · View workflow run →