kendo.dev

Appearance

Sprints ​

Sprints are timeboxed periods for focused work. kendo supports the full sprint lifecycle: planning, execution, and completion.

Sprint Lifecycle ​

1. Planning ​

Create a new sprint and assign issues to it. During planning:

  • Review the backlog and select issues for the sprint
  • Estimate effort and set priorities
  • Assign issues to team members

Only one sprint can be active at a time per project. Additional sprints stay in the planned state until the active sprint completes. A project can hold up to 50 open sprints (planned and active together) at once.

2. Active Sprint ​

Activate a sprint to start the timebox. During an active sprint:

  • The board filters to show sprint issues by default
  • Team members work through issues, moving them across lanes
  • Time can be logged against sprint issues

3. Completion ​

Complete a sprint when the timebox ends:

  • Issues in the final lane stay with the completed sprint
  • Unfinished issues move to a sprint you choose, or back to the backlog
  • The sprint moves to completed status

Automatic Sprint Cycle ​

A project can complete and start its sprints by itself. Switch it on under Settings → Sprint Settings; it is off until you do, and changing it needs the Projects: Update permission.

kendo checks every opted-in project once an hour:

  • An active sprint whose end date has passed is completed. "Passed" means the end date is before today by kendo's server clock, which runs on UTC, so a sprint ending on Friday is completed in the first check after midnight UTC — not at your local midnight.
  • If no sprint is active after that, the one planned sprint whose dates include today is started. A planned sprint whose end date has already passed is never started.
  • Unfinished issues follow the project's Unfinished issues setting. With Move to next sprint, they go to the sprint that was just started — or, when none started yet, to the project's only planned sprint as long as its end date has not passed, so a sprint ending on Friday hands its work to the one starting on Monday. With more than one planned sprint and none started, or when the only planned sprint has already ended, they go to the backlog. With Move to backlog, they always go to the backlog.
  • Issues in the final lane stay with the completed sprint, as they do when you complete it by hand.

The cycle never guesses. When two planned sprints are both due, it starts neither; when more than one sprint is active, it leaves the project alone until only one remains. In both cases, and when no planned sprint is due at all, the Backlog says why, so you can sort it out by hand; when no sprint is active, the Board says so too, in place of its usual "no active sprint" message.

Archived projects are not cycled. Every issue the cycle moves is recorded in the audit log as done by a scheduled job, not by a person.

Sprint Statuses ​

StatusDescription
PlannedSprint created but not yet started
ActiveCurrently running — only one per project
CompletedSprint finished, archived for reference

Managing Sprints via MCP ​

AI assistants can manage sprints through MCP tools:

"Create a new sprint called 'Sprint 12' in project KD"
"Complete the active sprint in project KD"

Available MCP operations: create, update, and complete sprints. See the API Reference for details.

See Also ​