Glossary
Esta página aún no está disponible en tu idioma.
One page, alphabetical, for when you need a definition and not a guide. For the guided tour, read Core concepts instead.
Archive — Filing a task away without deleting it. Archived tasks live in one place per project and come back to their original column in a click.
Assignee — The person doing a task.
Audit log — The record of who changed what and when. Admin-only, or a
manager holding audit.view.
Auto-archive — A schedule that archives old finished work. Takes a separate period for completed and canceled tasks.
Baseline — A snapshot of a plan’s dates, so later you can see the shape of a slip.
Board — The kanban layout. Columns are statuses by default.
Capability — A single right granted to a manager without promoting them to admin — for example, seeing everyone’s hours.
Channel — A chat room in the workspace.
Comment — A message on a task. Threaded, with reactions and mentions.
Custom field — A property you define yourself. Seven kinds, Pro.
Cycle — What the API calls a sprint. See Sprint.
Dashboard — A grid of widgets on a project, folder, or initiative.
Dependency — A blocking relation drawn as an arrow on the timeline.
Dialect — Which database the schema designer targets: PostgreSQL, MySQL, SQLite, or dialect-neutral Standard.
Dot — The AI agent inside dotby. Runs on your own model key.
Editor guest — A guest who can comment and edit. Counts against a per-seat allowance.
ERD — Entity-relationship diagram. See Schema designer.
Estimate — How big a task is, in points, t-shirt sizes, or time.
Folder — A group of related projects, with its own dashboard and cross-project views.
Guest — Someone with no workspace-wide access, who sees only the projects they were added to.
Inbox — Your personal feed of what changed that involves you.
Initiative — An outcome that spans several projects, with a lead, dates, a health trail, and a projected finish date.
Issue — What the API calls a task. See Task.
Label — A free-form tag. Anyone can create one; only an admin can delete one.
List — The dense table layout. Where bulk work happens.
Member — A teammate with workspace-wide access. Costs a seat.
Mirror — The same task appearing on a second project’s board. One task, two boards.
Module (work) — A named workstream inside a project — “Checkout”, “Onboarding”.
Module (product) — A surface an admin can switch off for the whole workspace — chat, wiki, whiteboards, ERD.
My Work — Everything assigned to you, across every project.
Page — A document beside the work. Same editor as a task description.
Placement — The mechanism behind a mirror: where a task sits on a particular board.
Priority — None, Urgent, High, Medium, or Low.
Project — A container of work with its own board, statuses, and members. Also the unit of access.
Project key — The short prefix that numbers a project’s tasks — WEB, so
WEB-1.
Rate — An hourly amount for one person doing one activity. Admin-set.
Relation — A typed link between two tasks: blocks, blocked by, duplicates, related to.
Role — Admin, manager, member, or guest. One per person per workspace.
Schema designer — The ERD surface: tables, columns, keys, relationships.
Seat — One paid member. Guests never take a seat.
Sprint — A fixed time box inside a project. The API calls this a cycle.
Status — A column in the workflow. Has a name and a type.
Status set — A reusable, named workflow you can apply to any project.
Status type — Backlog, Unstarted, Started, Completed, or Canceled. The type is what charts and rollups count.
Sub-group — A second grouping axis that splits a board into horizontal swimlanes.
Sub-task — A task nested under another task. Nests six levels deep.
Swimlane — A horizontal band on a board, produced by sub-grouping.
Task — One piece of work. The API calls this an issue.
Team — A named group of people you can mention as one handle.
Timeline — The Gantt layout. Bars on a calendar, with dependency arrows.
Trash — Where deleted projects wait for 7 days, and deleted workspaces for 30.
View — A saved combination of layout, filters, grouping, sort, and columns, shown as a tab.
Viewer guest — A read-only guest. Free and unlimited on every plan.
Whiteboard — An infinite canvas, standalone or embedded in a page.
Widget — One tile on a dashboard. Up to 30 per layout.
Workspace — Your company. Holds people, projects, settings, and billing. Data never crosses between workspaces.
Why the API says “issue” and “cycle”
Section titled “Why the API says “issue” and “cycle””The interface says task and sprint, because that is what teams say out
loud. The REST API and MCP tools use issue and cycle in paths and field
names, because those identifiers are part of a public contract and renaming them
would break every existing script.
They are the same objects. GET /v1/issues/WEB-42 returns the task you call
WEB-42.
| Interface | API |
|---|---|
| Task | issue |
| Sprint | cycle |
| Status | state |
- Core concepts — the same words, explained in order.
- REST API reference — where the API spellings appear.