Features
Projects and epics
Two grouping levels inside the workspace, and neither of them isolates anything.
A project is a filter label
It groups cards in the sidebar (All cards / No project / each project) and is not an isolated space: what isolates is the workspace. Deleting a project releases its cards: they go back to “no project”, because projectId is nullable.
An epic groups one delivery inside a project
The epic is the only entity that inherits the workspace rather than carrying it: Epic.projectId is required, and the workspace comes from the project. A loose epic does not exist, and that is why creating one does not ask for tenantId.
- A card only enters an epic of its own project. The rule holds in both directions: changing the card's project is checked too.
- An epic can have a date target. Cards entering it inherit the due date, and overwriting one already chosen takes an explicit ask (
alignDueAt). - An epic can be locked: it stops taking new cards. It is reversible and touches no card.
- Concluding an epic requires deciding the pending cards: those that have not reached the done column go there (
DONE) or into another epic (MOVE). There is no “leave it as it is”.
Epics are optional
The whole feature can be turned off in Settings, but turning it off deletes every epic, which is why the route requires the phrase REMOVER EPICS.