kendo.dev

Appearance

Projects ​

Projects are the top-level container for all work in kendo. Each project has its own board, sprints, epics, time entries, and team members.

Creating a Project ​

Create a project from the dashboard with a name and code. The project code is a short prefix (2-5 characters) used for issue keys. For example, a project with code KD generates issues KD-1, KD-2, and so on.

TIP

Choose a meaningful project code — it appears in branch names, commit messages, and MCP tool references. It cannot be changed after creation.

Board Configuration ​

Lanes ​

The Kanban board is organized into lanes that represent your workflow stages. Every project starts with default lanes, but you can customize them:

  • Add lanes for extra workflow stages (e.g., "QA", "Staging")
  • Rename lanes to match your team's terminology
  • Reorder lanes by dragging them into position
  • Remove lanes that are no longer needed (issues in that lane move to the backlog)

GitHub Triggers ​

Each lane can have a GitHub trigger configured. When an issue moves into that lane, kendo can automatically perform GitHub actions. See the GitHub integration guide for details.

Teams and Access ​

Projects are assigned to teams. All members of a team have access to the team's projects. User roles (Admin, Developer, Viewer) determine what actions each member can perform.

See the Quick Start for role descriptions.

Epics ​

Epics group related issues on a timeline. Each epic has:

  • Name and description
  • Start date and end date for timeline visualization
  • Status — Open, In Progress, or Completed
  • Color for visual identification on the timeline

Create epics from the project's epic view, then assign issues to them. Epics help plan larger features that span multiple sprints.

Multi-Tenant Isolation ​

Each tenant in kendo gets a fully isolated database. Projects, issues, users, and all data are separated at the database level — there is no cross-tenant data access.

Audit Logging ​

All changes to projects, issues, users, and settings are recorded in an append-only, hash-chained audit log. This provides a tamper-proof history of who changed what and when.

See Also ​