Epics, subtasks and linked tickets
Tickets rarely stand alone. KAMI Tasks gives you three ways to relate them, and each answers a different question.
Epics — "what initiative is this part of?"
An epic is a ticket of type Epic that other tickets belong to. Use one per larger initiative — a feature, a migration, a client project — and put the tickets that deliver it inside.
- On the ticket page, set the Epic field, and the epic's own page lists every ticket in this epic.
- On the Kanban board, tickets group into lanes by epic, so the board reads as initiatives rather than a single pile.
- You can move a ticket into an epic straight from the board's right-click menu — Move to epic.
- Sprint Insights tracks epic progress, so you can see how far each initiative has come.
Subtasks — "what are the steps of this ticket?"
A subtask is a child of one ticket: a step of the work, not a piece of work in its own right. Add them from the ticket page with Add subtask.
Use subtasks when one person's ticket has several checkable stages. If a "subtask" needs its own assignee, sprint and estimate, it is really a ticket — make it one and put it in the same epic instead.
Linked tickets — "what else should the reader know about?"
Linked tickets connect two tickets without any hierarchy: a duplicate, a dependency, related work in another project. Add one with Add link on the ticket page.
A link is a signpost for the reader, nothing more — it doesn't move status, block anything, or affect reports.
Choosing between them
| You want to say | Use |
|---|---|
| "This ticket is part of the payments revamp" | Epic |
| "This ticket has four steps" | Subtasks |
| "See also KDV-88, it's the same area" | Linked ticket |