Hierarchy

Planning in Agilerr follows a strict hierarchy:

flowchart TD
  P[Project] --> E[Epic] --> F[Feature] --> S[User Story] --> T[Task]
  P -.-> B[Bug: outside the hierarchy]

Level	Use it for
Project	A product or body of work. Everything lives in a project.
Epic	A large outcome, such as “Customer onboarding”.
Feature	A capability that delivers part of an epic.
User Story	A user-visible behaviour, usually written “As a … I can …”.
Task	A unit of delivery work for the team.

An item can only sit under the level directly above it (a task under a story, a story under a feature, and so on). Epics sit directly under the project.

Note

Tasks are intended for delivery teams. They are never generated by AI Add.

Bugs are separate

Bugs are not part of this tree. They live on the project-wide Bugs page. See Bugs.

What every item has

Field	Notes
Title	required
Type	epic, feature, story, task or bug
Status	see Statuses
Description	Markdown
Assignee	any user
Tags	free-text labels
Parent	the item directly above it
Comments	Markdown, with mentions

Colours

Each type and status has a colour, which you can change in project settings. The coloured bar on the right of a card shows its status.