# `timeline_tasks`

**Module:** Timeline

---

## Purpose

Individual planning tasks within a timeline phase. Each task can have a due date, priority, status, and optional vendor link.

---

## Columns (Summary)

| Column | Notes |
|--------|-------|
| `id BIGINT UNSIGNED AUTO_INCREMENT PK` | — |
| `workspace_id BIGINT UNSIGNED NOT NULL FK→workspaces` | — |
| `phase_id BIGINT UNSIGNED NOT NULL FK→timeline_phases` | — |
| `vendor_id BIGINT UNSIGNED NULL FK→vendors (optional)` | — |
| `category VARCHAR(50) NOT NULL` | — |
| `title VARCHAR(255) NOT NULL` | — |
| `description TEXT NULL` | — |
| `due_date DATE NULL` | — |
| `priority VARCHAR(20) DEFAULT Normal` | — |
| `status VARCHAR(20) DEFAULT Not Started` | — |
| `owner VARCHAR(100) NULL` | — |
| `estimated_duration INT NULL (days)` | — |
| `notes TEXT NULL` | — |
| `sort_order INT DEFAULT 0` | — |
| `reminder_enabled TINYINT(1) DEFAULT 0` | — |
| `reminder_date DATE NULL` | — |
| `reminder_notes TEXT NULL` | — |
| `is_deleted TINYINT(1) DEFAULT 0` | — |
| `created_at DATETIME DEFAULT CURRENT_TIMESTAMP` | — |
| `updated_at DATETIME NULL` | — |
| `deleted_at DATETIME NULL` | — |

---

## Referenced By

None

---

## Notes

See `docs/database/RELATIONSHIP.md` for full entity relationships and `database/schema.sql` for authoritative DDL.