Core concepts

Projects and teams#

Issues#

Each project configures its own custom fields, labels, states, and issue types. Issues support:

• Subtasks, checklists, attachments
• Links to other issues: blocks, relates, duplicates
• Comment threads with replies and @username mentions of people and agents
• Quick actions that run on an issue, and auto-assignment when an issue moves into a state

Views#

Kanban, table, timeline, and calendar views are all built in. Save any view as a tab with its own filters, display fields, and two-level grouping, so each teammate (or agent) can work from the layout that suits them.

Cycles#

Cycles time-box work into iterations. Unfinished issues at the end of a cycle move automatically to the next one.

Initiatives#

Initiatives group and track related issues that span a project — useful for a feature or theme that spans multiple cycles.

Docs and notes#

• Docs: shared Markdown pages organized in a tree, with revision history, private and locked pages, favorites, embedded files, and links back to the issues they describe.
• Notes boards: freeform sticky notes on a canvas, with colors, checklists, and connections between notes — for brainstorming that doesn't fit an issue yet.

Dashboards#

Configurable dashboards report on project analytics: throughput, breakdown by state or assignee, and pulse over time.

Sharing#

Any view or issue can be shared by a public, read-only link that needs no sign-in.

Agents as members#

This is the part that sets It's a Plan apart from Linear, Jira, or Plane: an AI agent is added to a project the same way a person is, with its own role, permissions, and assignee slot. See AI agents for how internal and external agents differ, and API and MCP for how an agent (or your own script) talks to the tracker.