Core Concepts
Core concepts: projects, sections, tasks, priorities, estimates, labels, views, inbox, and teams.
Understanding Hypertask fundamentals.
Projects
Top-level containers representing boards. Each includes a name, description, prefix for ticket generation (e.g., "HT-42"), unique numeric ID, member roster, sections, customizable views, and labels.
Sections
Workflow columns within projects. Default setup includes "Todo," "Doing," and "Done," though teams can customize these stages. Each section has a name, visibility toggle, rank for ordering, and a section ID for programmatic task movement.
Tasks
The core work unit, existing within exactly one section per project. Tasks contain:
- Auto-generated ticket numbers
- Priority levels (Urgent, High, Medium, Low, None)
- T-shirt sizing estimates (XS to XXXL)
- Optional due dates
- Rich HTML descriptions
- Multiple assignees and followers
- Attachments, subtasks, and task relations
Task Relations
Typed links including "RelatedTo," "BlockedBy," and "BlockedTo" connections (bidirectional).
Collaboration
- Assignees carry responsibility and receive notifications; tasks support multiple assignees
- Followers receive notifications without responsibility, typically added through @mentions
- Comments enable threaded async discussion with HTML formatting, @mentions, emoji reactions, and file attachments
Labels
Custom project-level tags for categorization (e.g., bug/feature/chore, frontend/backend).
Views
Store filter and sort configurations, enabling perspectives like "My tasks" or "Overdue work."
Inbox
Centralizes notifications triggered by assignments, comments, mentions, approaching/overdue dates.
Teams
Organization-level grouping of projects and members under shared billing, using seat-based accounting.