It’s a Plan
Upgrade to Pro
Navigation
Features

Everything the tracker does

It's a Plan is an open-source issue tracker you host yourself. Every part below works on the same issues, so nothing gets copied between tools.

Star on GitHubSee the product

01

AI agents

Give issues to AI agents, like you would to a teammate.

Delegate an issue or @mention an agent, and it hands the work back for review. Or give it a schedule, like a release notes draft every Friday. It runs in the app or on your machine, with the coding CLI you already use.

Read about AI agents
itsaplan.dev/IAP-62
IAP-62

Login redirect drops the return URL

MV

Mira Vos @Triage Bot please take this one.

Triage Botis working on IAP-620:41
  1. Read IAP-62 and three linked issuesget_issue · list_issue_activity
  2. Replied with the cause and a fix planadd_comment
  3. Opening IAP-74 for the expired session casecreate_issue · link_issues

Triage Bot The OAuth callback drops the return URL. I will keep it in the state parameter and add a test.

  1. 02

    Views

    See the same issues as a board, table, timeline or calendar.

    Save a filter as a view. Share it as a read-only link that opens without a login.

    Read about Views
  2. 03

    Docs

    Write specs in the same project as the issues.

    Your team edits a page at the same time. Select a line to turn it into an issue.

    Read about Docs
  3. 04

    Notes

    Sketch a plan before it turns into issues.

    Put sticky notes on a canvas and connect them with lines. Write the issues when the idea is ready.

    Read about Notes
  4. 05

    Dashboards

    Put the numbers people keep asking for on one screen.

    Add widgets for counts, trends and a projected finish date. They read the live issues, so nobody exports a spreadsheet.

    Read about Dashboards
  5. 06

    Initiatives

    Know early if a goal will slip.

    Put issues under a goal with a target date. Progress comes from their status, so nobody updates it by hand.

    Read about Initiatives
  6. 07

    Cycles

    Plan two-week sprints and carry over what is left.

    A new cycle starts with its name and dates filled in. When one ends, move the unfinished issues to the next in one step.

    Read about Cycles
Side by side

Which area you need

Every area works on the same project, so nothing here is a choice you have to make up front.

AreaReach for it whenWorks onWhat comes with it
AI agentsWork can go to a model, not a person.Issues, comments and tasks on a schedule.A model per agent, allowed actions, skills, tools, runners, run history.
ViewsThe same issues need reading a different way.Issues and every field on them.Four layouts, stacked filters, saved views, public links, bulk edit.
DocsThe work needs a spec, a guide or a decision written down.Pages in a tree, linked to issues and initiatives.Editing together, comments, mentions, version history, private and locked pages.
NotesThe thinking is not issues yet.Free-form notes on a shared canvas.Rich text, checklists, eight colors, connectors, boards per project.
DashboardsSomeone keeps asking the same question.Counts and trends over the project.Number, breakdown, throughput, burnup, pulse, activity and agent widgets.
InitiativesA goal spans more issues than one board shows.Groups of issues from across the project.Owner, priority, target date, health, progress from issues.
CyclesThe team plans its work in sprints.Issues planned into sprints, two weeks by default.Prefilled dates, carry-over of unfinished issues, cycle history on each issue.