Subjects & Epics
Work in Ticku is organized in a hierarchy, and the exact shape depends on the project type.
The hierarchy
Project → Subject (folder) → Ticket → Sub-task
- A Subject is a folder that groups related tickets. Every ticket lives in a Subject.
- A Ticket is the unit of work (called a Task in Consulting/Dev projects).
- A Sub-task is a checklist-style item under a ticket.
Naming changes per project type:
| Project type | Folder | Item | Child |
|---|---|---|---|
| Support | Subject | Ticket | Sub-task |
| Consulting | Subject | Task | Sub-task |
| Dev | Subject | Task | Sub-task |
| Epic | (none) | Epic | (none) |
See Project Types for the full comparison.
Subjects (folders)
- Every Subject has a time window (start/end) — all subjects are time-based.
- Tickets are created inside a Subject and inherit its context; a ticket's dates are validated against its Subject's window.
- Subjects have a sort order so you can arrange them.
Creating and editing Subjects is a lead-tier permission (workspace:subjects:*) — see Roles & Permissions.
Epics
Epic projects are different: they have no Subject folders and no sub-tasks. Their tickets (called Epics) attach directly to a hidden default folder. Epics use a simplified workflow — Active (Open), On Hold, Deferred, Closed, Reopened — and have no assignees-driven statuses like In Progress or Review.
Linking projects to an Epic
Other projects can roll up to an Epic. A project links to one or more Epic tickets (via ProjectEpicLink), so a high-level Epic can track progress across several delivery projects. This is how Ticku models a big initiative made of many smaller projects.
Related
- Tickets — working with individual tickets
- Tasks — sub-tasks
- Bulk Upload — create Subjects/tickets/sub-tasks in bulk