Projects and tasks
What a project holds, what a task holds, and the identifiers you will paste into chat.
Projects
A project is the boundary for a body of work. It owns:
- Its own statuses and the workflow that connects them
- Its own task types — bug, feature, chore, whatever you define
- Its own priorities, labels, milestones and sprints
- Its own members, who are the only people who can see its tasks
That last point is worth stating plainly: project membership decides visibility. A workspace member who is not in a project cannot see its tasks, cannot find them in search, and gets a "not found" rather than a "no permission" if they guess a task key. There is no difference between "this does not exist" and "this is not yours" from the outside, on purpose.
The project key
APOLLO, WEB, OPS — up to seven characters. It prefixes every task key in
the project and is fixed at creation.
Tasks
A task is one piece of work. It carries:
| Key | krrim-0042 — stable for the life of the task |
| Title and description | The description is rich text: headings, lists, checklists, code blocks, images |
| Type | Bug, feature, chore — whatever the project defines |
| Status | Where it is in the workflow |
| Priority | |
| Assignee | One person accountable |
| Dates | Start, due, and an estimate |
| Milestone / sprint | Optional, and not the same thing — see Sprints and milestones |
| Labels | Free-form tagging |
| Custom fields | Whatever else your workspace records |
And it holds: subtasks, comments, attachments, time entries, dependency links, followers and a full activity history.
Task keys
krrim-0042 is the identifier people use. It is what appears in notifications,
what you paste into a chat message, and what turns into a link when you do.
Keys are never reused and never renumbered — a task moved between milestones,
sprints or assignees keeps its key.
Pasting a task key into a comment turns it into a live link with the task's current title and status. You do not have to paste URLs.
Subtasks vs dependencies
These get confused, and they mean different things:
- A subtask is part of its parent. Breaking "Ship checkout v2" into six pieces of work that together are the whole thing.
- A dependency is a task that must happen before another. Two independent pieces of work, one of which is waiting.
Use subtasks for decomposition and dependencies for sequencing. See Dependencies.
Followers
Anyone can follow a task to get its notifications without being its assignee. You are added automatically when you comment on one or are mentioned in it. Unfollow from the task's own menu.