Sprints & Releases

Updated

One Entity, Not Two

A sprint and a version are the same thing, so Kwilio Projects has one entity rather than two. Name it "Sprint 12" or "v2.1" — either way it is a dated bundle of work belonging to one project, and only that project's tasks can join it.

Creating a Release

  1. Open a project → Releases
  2. Click New Release
  3. Name it, and give it a start date, an end date, or both

Partial dates are fine and still say something. On the timeline, an end date alone becomes a milestone; a start date alone runs to today.

Adding Work

Add tasks to a release from the release itself or from the task. A task belongs to at most one release — adding it to a sprint takes it out of the last one, so a task is never counted twice.

Deleting a release unschedules its tasks. It never deletes work.

Shipping Is Guarded

A release refuses to close while tasks are still open. You have two honest options:

  • Finish the work, then ship
  • Move the open work out of the release and ship what actually landed

Either way, the release records what shipped rather than what was hoped for. The date you planned stays visible next to the date you shipped, so a slipped release stays legible after the fact instead of quietly rewriting itself.

Marking a release shipped is a project lead's call — it needs owner or admin access, not plain edit access.

Timeline

The timeline lays releases out against the calendar, with a filled bar for the work that is finished and a red line for today.

  • Colour matches the status chips used everywhere else, so a release keeps one identity across views
  • Every row carries its name and status, not colour alone
  • You can toggle the tasks inside each release on and off

Release Notes

Kwilio Projects can draft release notes from what's in the release, reconciled against your repositories — and it reports the disagreements rather than smoothing them over. See AI Features.