croffasia/itsaplan

If your team already lives in Linear or Jira and you want agents to pick up tickets without building a separate orchestration layer, this is worth a look — but only as an experiment, because the project says breaking changes are expected before a stable release.

The problem

A team plans work in a tracker, then wants an AI agent to take some of those issues: triage a bug, draft a spec, or open a pull request. Today that usually means copying the issue into a chat tool or coding CLI, losing the link back to the ticket and any record of who did what. In It's a Plan, the agent is a project member with a role, permissions and an assignee slot, so the ticket stays the unit of work and the agent acts on it in place. The result is one board where you can see both human and agent assignments, rather than a tracker plus a parallel pile of prompts.

What's different

Agents run either internally on any model or externally through your coding CLI, and a run can start from an @mention, an assignment, or a schedule. The surrounding product is not an afterthought: kanban, table, timeline and calendar views, cycles that roll unfinished issues forward, custom fields, dashboards with throughput and burnup projections, and docs with revision history. A REST API with OpenAPI, an MCP server and webhooks give agents and scripts a documented way in, and pull requests from five forges are surfaced alongside issues.

The main trade-off is maturity. The README states the project is under active development and to expect breaking changes before the first stable release, so schema or API shifts are a real possibility. The edition split also matters: the free Community edition allows one workspace per person and one OIDC provider plus one SCIM setup for the instance, while multiple workspaces, per-workspace SAML/OIDC and SCIM, and an audit log with before-and-after changes sit in Pro. For a small team that only needs one workspace, the free tier covers the core tracker; a larger organization evaluating it as a Jira replacement will hit the Pro boundary quickly.

Who should try it

Good fit: a small self-hosting team that wants an issue tracker it controls, is comfortable running PostgreSQL and Docker, and is curious about giving agents real assignee slots on the same board. It also suits teams that want to try the agent workflow without committing — the README notes you can use it as a plain tracker and never turn on a single agent.

Poor fit: an organization that needs a stable API and data model now, or one that depends on per-workspace SSO/SCIM and audit trails without buying Pro. Teams unwilling to maintain a server should note the recommended path is a one-click Railway deploy, which still requires owning a domain; there are also Coolify and Kubernetes/Helm paths for those already running that infrastructure.

Requirements and limitations

Self-hosting needs Docker and Bun for the local trial, which starts the stack on localhost with generated secrets. The production route differs: the Railway template needs two hostnames and a domain you own, and the guide explains what to do after deploy. Ongoing upkeep means tracking releases and migrations during the pre-stable period, plus backing up your own PostgreSQL data since nothing is hosted for you.

The licensing is AGPL-3.0 with the runner package under Apache-2.0, and a commercial licence is offered for companies where AGPL does not fit. Agent runs depend on your own model API keys or your coding CLI, so cost and model choice stay your responsibility. The README also points to private vulnerability reporting rather than public issues.

HotRepo's take

The repository is 103 days old as of the tracked sample. HotRepo recorded one weekly observation: +586 stars on the TypeScript weekly board, rank #15, dated 2026-10-26. With no comparable daily-board history, persistence cannot be judged from these signals alone. Before adopting, check the documented self-hosting and update guidance, and confirm whether the Community single-workspace limit fits how your team actually organizes projects.

Project source and documentation