Epics and Sprints

Epics and sprints are two ways to group tasks into larger units. They have different purposes, so you can use them together or independently.

Epic

A larger goal or feature bundle that spans quarters or half-years.

• When to use: things like "Introduce payments" or "Onboarding revamp" that span multiple sprints
• Properties: name, description, color, status (OPEN/COMPLETED)
• Relation to tasks: each task belongs to at most one epic
• Visual: an epic-colored chip appears on kanban cards

Creating an Epic

Project → Epics tab → + Epic. Color is shown on cards at a glance, so use color to encode categories (e.g., blue = infra, orange = customer experience).

Sprint

An execution batch of 1–2 weeks.

• When to use: when you want to lock in this week's commitments and focus
• Properties: name, range (start/end), status (PLANNING / ACTIVE / COMPLETED)
• Active sprint: only one ACTIVE sprint allowed per project
• Auto-close: at end date, you're asked what to do with incomplete tasks

Sprint Lifecycle

1. PLANNING: pull tasks from the backlog into the sprint
2. ACTIVE: one click activates on start day
3. COMPLETED: at end day, run retro and handle incomplete tasks

Using Both Together

• A single epic ("Introduce payments") can contain tasks spread across several sprints.
• Reports and analytics aggregate by both units.

Next Steps

• For progress and velocity, see performance reports.
• For filtering boards by epic color, see Boards and Views.