Projects, epics, tasks and tags
The things Sparrow keeps, and the statuses and authorship a task can have.
-
A project has a key, such as
SPR, an owner and members. Members create, change and delete its epics, tasks, tags and relationships. Only the owner can change or delete the project itself, add or remove members, or hand the project to another member. -
An epic groups tasks towards one objective. Its objective is one paragraph, shown with bold, italic and
code; headings, lists, tables, quotes, code blocks, images, links, HTML and blank lines aren't accepted. The owner of several projects can share an epic across them: each project gets its own copy, and the name and objective are kept in step (Sharing an epic across projects). -
A task is numbered within its project (
SPR-12). It's a story or a bug, has an optional epic and an assignee, carries the project's tags, and sits in one board column, its status. What each status means, and every move between them, is in the task status workflow.Each board column lists its tasks most recently updated first, and shows the first ten. When a column holds more, its
…button opens Search filtered to that project and status.A task's authorship says how it came to exist, and the board card shows it in place of the assignee:
Authorship Who created it Card shows Manual You, in the dashboard MichaelDirected An agent, because you asked it to Michael + AgentIndependent An agent that found the need and filed it itself AgentAn agent creating a task through the MCP server says which it is with
create_task'sdirected(true when you asked). It's set when the task is created and never changes (ADR-0020). -
Relationships link tasks: one task blocks, relates to or duplicates another.