Terms
Terms are listed alphabetically. Click any anchor link to share a direct reference.
- Backlog #
- A list of issues that are not yet assigned to a board column or sprint. Issues live in the backlog until they are moved to the board (Kanban) or added to a sprint (Scrum). See Boards.
- Board #
- A visual workspace where issues move through columns representing stages of work. Boards belong to a project and are either Kanban or Scrum type. See Boards.
- Column #
- A stage of work on a board (example: To do, In progress, Done). All boards in a workspace share the same column definitions. Columns are managed in Workspace Settings → Board columns.
- Epic #
- An issue of type Epic that can contain child issues. Epics represent a large piece of work broken down into smaller tasks. Child issues can be generated automatically using AI Split Epic.
- Intake column #
- The first (leftmost) column on a Kanban board. When an issue is moved from the backlog to the board, it lands in the intake column.
- Issue #
-
The core unit of work in Ouraboard — a task, bug, feature, or epic. Every issue belongs
to a project, has a unique slug (example:
PRJ-42), and can be assigned, prioritised, and labelled. See Issues. - Issue type #
- A category applied to an issue (example: Bug, Feature, Task, Epic). Issue types are configurable per workspace in Workspace Settings → Issue types.
- Label #
- A free-form tag applied to an issue for grouping and filtering. Multiple labels can be applied to a single issue. Labels are configurable in Workspace Settings → Labels.
- Organization #
-
The top-level container in Ouraboard. An organization owns one or more workspaces and
defines your URL handle (example:
acme.ouraboard.app). Billing is scoped per workspace, not per organization. See Organization & workspace. - Priority #
- An urgency level assigned to an issue (example: Urgent, High, Medium, Low). Priorities are configurable per workspace in Workspace Settings → Priorities.
- Project #
- A grouping container inside a workspace that holds boards and issues (example: Mobile App, Backend API). Issues belong to exactly one project and cannot be moved between projects after creation.
- Slug #
-
A short, unique identifier for an issue (example:
PRJ-42). Slugs are assigned automatically and cannot be changed. Including a slug in a commit message or pull request title automatically links that commit or PR to the issue. See GitHub integration. - Sprint #
- A time-boxed period (typically 1–4 weeks) on a Scrum board during which a fixed set of issues is worked on. Only one sprint can be active per board at a time. See Boards — Sprints.
- Story points #
- A numeric estimate of the effort required to complete an issue. Used for sprint capacity planning on Scrum boards. The scale (1–5, Fibonacci, etc.) is up to the team.
- Team #
- A named group of workspace members used to organise and filter issues. Teams are an organisational grouping — they do not grant additional permissions. Available on the Team plan. See Teams.
- Workspace #
- A delivery area inside an organization that contains projects, boards, and members. Each workspace has its own billing plan, member list, and settings. See Organization & workspace.