It’s a Plan
Cycles

Run sprints without the admin work

A cycle in It's a Plan is a sprint, two weeks by default or any dates you set. Plan issues into it and carry the unfinished ones into the next cycle in one step.

itsaplan.dev/cycles / sprint-13
CyclesSprint 13
Active·Oct 19 – Nov 1

Sprint 13

Ship the new status page and the alert rules.

12/19
Filter

Todo3

BCN-27

Add a down migration for the events table

MV
BCN-33

Retry webhook deliveries

SK

In Progress4

BCN-10

Status page v2: new public layout

MV
BCN-29

Group incidents by service

JO

01 · Plan

The next cycle is already filled in

The name continues the numbering and the start date follows the last cycle. It runs two weeks unless you pick another length. Change what you need, then create it.

Sprint 16 starts on Mon, Nov 30, the day after Sprint 15 ends, and runs for 2 weeks.

1 week2 weeks3 weeks4 weeksor set the dates by hand

02 · Track

Every sprint on one list

The active cycle comes first, then the upcoming ones. Open a cycle to see its issues on a board, table, timeline or calendar.

  • Sprint 13ActiveOct 19 – Nov 1 · 6d left
    12 of 19 done
  • Sprint 14UpcomingNov 2 – Nov 15
    6 issues planned
  • Sprint 15UpcomingNov 16 – Nov 29
    nothing planned yet
  • Sprint 12CompletedOct 5 – Oct 18
    in the archive

03 · Finish

Carry the unfinished work forward

When a sprint ends with work still open, move all of it to the next cycle in one step. Nobody drags issues one by one.

7

unfinished issues move to Sprint 14

  • Status page v2: new public layoutBCN-10
  • Add a down migration for the events tableBCN-27
  • Retry webhook deliveriesBCN-33
  • and 4 more

Start the next one today

When the next cycle is already planned, it starts now and keeps its end date. Unfinished issues move into it.

Or finish early

The cycle closes today. You pick where its unfinished issues go, or leave them on it.

Done work stays put

Finished and canceled issues stay on the cycle they were closed in.

04 · History

See which issues keep slipping

An issue that sat in two or more cycles shows a 3 badge next to its cycle, so a stuck task is easy to spot.

BCN-27Add a down migration for the events table

  • Planned into cycle Sprint 11Sep 21
    Mira Vos
  • Moved from cycle Sprint 11 to Sprint 12Oct 5
    Sam Kerr
  • Moved from cycle Sprint 12 to Sprint 13Oct 19
    Sam Kerr
Details

The rest of it

01

Drag on the timeline

Move a cycle or change its length by dragging its bar.

02

Filter by cycle

Show the active cycle, the upcoming ones or issues with no cycle, in any view.

03

Agents plan too

An AI agent can create cycles and move issues between them.

04

Bring your sprints

An import from Linear or Plane brings its cycles along.

05

API and MCP

Scripts and agents create, finish and start cycles through the REST API and the MCP server.

06

Off when you need it

A project that does not work in sprints switches cycles off in its settings.

Start planning on your own terms

Self-host it today and have your team tracking work by tonight.

Or deploy to Railway in one click

AGPL-3.0 · No per-seat fees · Use your own AI key or subscription