Appearance
Issues & Board
Issues are the core unit of work in kendo. They live on a Kanban board where you can drag them between lanes, assign team members, set priorities, and track progress through your workflow.
Creating Issues
Create issues from the board view or the backlog. Each issue gets a unique key based on the project code (e.g., KD-42).
Issue Fields
| Field | Description |
|---|---|
| Title | Short summary of the work |
| Description | Detailed explanation with Markdown support |
| Type | Feature or Bug |
| Priority | Low, Medium, High, or Critical |
| Assignee | Team member responsible for the issue |
| Lane | Current board position (workflow stage) |
| Sprint | Optional sprint assignment |
| Epic | Optional epic grouping for timeline planning |
The Board
The Kanban board shows all issues organized by lane. Drag issues between lanes to update their status.
Filtering
Filter the board by:
- Sprint — Show only issues in the active sprint
- Assignee — Focus on one team member's work
- Search — Find issues by title or key
Keyboard
The board is a single Tab stop. Tab onto it and focus lands on one issue. Tab again leaves the board. You don't have to tab through every issue.
| Key | Action |
|---|---|
| ↑ / ↓ | Previous / next issue in the lane |
| ← / → | Same position in the previous / next lane. Lanes without issues are skipped. |
| Home / End | First / last issue in the lane |
| Ctrl/Cmd+Home / Ctrl/Cmd+End | First / last issue on the board |
| Enter | Open the issue |
| M | Open Move to lane (if you're allowed to edit issues). ↑ / ↓ pick a lane, Home / End pick the first / last lane, Enter moves the issue, Esc closes the menu. |
| C | Copy the issue key |
| A | Assign yourself (unassigned issues you're allowed to edit) |
A moved issue lands at the top of its new lane, and focus moves with it. After G, the next letter goes to the G-shortcuts as everywhere else, so G then M still opens My issues. With no issues on the board, ← / → scroll the lanes.
To jump to one issue, type its title or key in the search box, then Tab past the remaining filter-bar controls to reach it.
Backlog
Issues not assigned to a lane or sprint live in the backlog. Use the backlog to triage incoming work and plan upcoming sprints.
Blocking Relationships
Issues can have blocking dependencies:
- Blocks — This issue blocks other issues from being started
- Blocked by — This issue cannot start until its blockers are resolved
Blocking relationships help your team understand dependencies and prioritize work that unblocks others. Both directions are visible on the issue detail view.
Attachments
Upload files to issues for reference — screenshots, design mockups, logs, or any supporting material. Attachments are stored per issue and visible to all team members with access.
Comments
Discuss issues with your team through comments. Comments support Markdown formatting and @mentions — mentioning a team member sends them a notification.
Activity
The Activity tab on an issue lists its creation and later changes to lane, priority, type, assignee, sprint, epic, title, description or estimate, with who made each one — or System, where a GitHub webhook drove it — and when. See Audit Logging for what is and is not recorded.
Bulk Operations
Select multiple issues to perform bulk operations like deletion. This is useful for cleaning up the backlog or removing duplicate issues.
Working with Issues via MCP
AI coding assistants can manage issues through kendo's MCP tools:
"Create a feature issue: Add pagination to the issues list"
"Move KD-42 to In Progress"
"Search for issues about authentication"Available MCP operations: create, update, delete, move, and search issues. See the API Reference for details.
See Also
- Quick Start — Creating your first issues
- Sprints — Assign issues to sprints
- Time Tracking — Log time against issues
- Projects — Configure board lanes and epics