Section
A special type of task used to organize and group related tasks within a project.
Definition
A section is an organizational tool within a Project that groups related Tasks together. Think of it as a divider or heading within your project.
Key Characteristics
Not a Task
Sections are organizational only:
- Cannot be completed (no checkbox)
- Cannot have due dates
- Cannot have tags
- Used purely for grouping
Contains Tasks
Sections hold tasks beneath them:
📦 Planning Phase (Section)
□ Define requirements
□ Create wireframes
□ Get approval
📦 Development Phase (Section)
□ Frontend development
□ Backend developmentTwo Types
Sections can be Parallel or Sequential, just like Project Types.
Section Types
Parallel Section
Tasks can be completed in any order.
Example: "Development Phase"
- Frontend development ✓
- Backend development ✓
- Database design ✓
All can be done simultaneously.
Sequential Section
Tasks must be completed in specific order.
Example: "Launch Phase"
- Testing
- Bug fixes
- Deploy to production
Must be done in sequence.
Creating Sections
In Project View
- Open a project
- Tap + button
- Select "Add Section"
- Name your section
- Choose type (Parallel or Sequential)
- Save
Quick Method
Long press on empty space in project → "Add Section"
Using Sections Effectively
Example: Product Development
📋 Product Development Project
📦 Planning Phase (Sequential)
├── Define requirements
├── Create wireframes
└── Get stakeholder approval
📦 Development Phase (Parallel)
├── Frontend development
├── Backend development
└── Database design
📦 Launch Phase (Sequential)
├── Testing
├── Bug fixes
└── Deploy to productionSection Interactions
Expand/Collapse
- Tap arrow next to section name
- Hides/shows tasks within section
- Useful for focusing on one phase at a time
Reordering
- Drag sections to reorder them
- Tasks move with their section
Adding Tasks
- Swipe right on section → "Add Task"
- Or drag existing task into section
Sections vs Subtasks
| Section | Subtask |
|---|---|
| In projects | Under tasks |
| Cannot be completed | Can be completed |
| Organizational only | Actual work item |
| One level only | Can be nested |
When to Use Sections
✅ Good Use Cases
Project phases:
- Planning, Execution, Review
Categories within project:
- Frontend, Backend, Design
Workflow stages:
- To Do, In Progress, Done
Time periods:
- Q1 Tasks, Q2 Tasks
❌ When NOT to Use
Simple projects: 3-5 tasks don't need sections
Over-organization: Too many sections adds complexity
Subtask alternative: Use Subtasks for task breakdown
Best Practices
Clear Names
Use descriptive section names:
- ✅ "User Research Phase"
- ✅ "Backend Development"
- ❌ "Misc"
- ❌ "Other"
Logical Grouping
Group related tasks:
- By phase (Planning, Execution)
- By component (Frontend, Backend)
- By time (Week 1, Week 2)
Limit Sections
- 3-5 sections per project
- Too many = harder to navigate
- Consider splitting into multiple projects
Sequential for Phases
Use sequential sections for project phases that must be done in order.
Parallel for Components
Use parallel sections for independent work streams.
Section Status
Sections don't have status, but you can:
- Collapse completed sections
- Move completed sections to bottom
- Archive project when all sections done