# AI use cases for Itsaplan (croffasia/itsaplan) Repo: [croffasia/itsaplan](https://github.com/croffasia/itsaplan) | Use cases: 4 | Page: https://dedupedai.com/use-cases/croffasia-itsaplan/ It's a Plan is a self-hosted, open-source project management and issue tracker where AI agents work on the same boards as people. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run a self-hosted issue tracker on your own machine: https://dedupedai.com/use-cases/croffasia-itsaplan/run-self-hosted-issue-tracker-locally/ - Assign an internal AI agent to issues on the team board: https://dedupedai.com/use-cases/croffasia-itsaplan/assign-internal-agent-to-team-issues/ - Route issues to a coding agent on your own machine: https://dedupedai.com/use-cases/croffasia-itsaplan/run-coding-agent-on-own-machine/ - Link pull requests to issues and move them on merge: https://dedupedai.com/use-cases/croffasia-itsaplan/link-pull-requests-to-issues-automatically/ ## How to run a self-hosted issue tracker on your own machine with Itsaplan Repo: [croffasia/itsaplan](https://github.com/croffasia/itsaplan) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Start the full It's a Plan stack in Docker on localhost and try boards, cycles, and docs. **Who it is for:** A team lead or developer who wants to evaluate an open-source alternative to Linear or Jira without a SaaS account. **The problem:** Hosted trackers charge per seat and lock data in a vendor's cloud, which makes trying a new tool costly and slow. **The outcome:** A running instance on localhost with kanban, table, timeline, and calendar views, ready for a first project. ### Steps 1. Install Docker and Bun, then clone the repo with `git clone https://github.com/croffasia/itsaplan.git`. 2. Change into the folder with `cd itsaplan` and install dependencies with `bun install`. 3. Run `bun run setup` and answer "Try it" when asked. 4. Open the address the setup prints, create an account, and create your first project. 5. Run `bun run setup` again later to restart the instance. Your data stays. ### Prompt to paste into your agent ```text In the itsaplan repo at , run `bun install` and `bun run setup`, answering "Try it". Report the local URL the setup prints and confirm that the Kanban, table, timeline, and calendar views load for a new project. ``` ### Caveat The README says the project is under active development and expects breaking changes before the first stable release, so do not treat a try-out instance as production. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/croffasia-itsaplan/run-self-hosted-issue-tracker-locally/ ## How to assign an internal AI agent to issues on the team board with Itsaplan Repo: [croffasia/itsaplan](https://github.com/croffasia/itsaplan) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Add an agent as a project member so it takes assigned issues next to your people. **Who it is for:** A product or ops lead who has a backlog of routine issues and wants an agent to work through some of them on the same board. **The problem:** Routine tickets wait in the queue because the team has no spare capacity, and agents often run outside the tracker where nobody sees their work. **The outcome:** An internal agent holds its own assigned issues on the board, and its runs start from an assignment, an @mention, or a schedule. ### Steps 1. Open the instance and add an internal agent as a project member with its own permissions. 2. Set the agent's model, system prompt, tools, and any reusable skills. 3. Assign an issue to the agent, or @mention the agent in a comment on an issue. 4. Open the agent's built-in chat to check its conversation history and the run result. 5. Adjust the agent's permissions or instructions if its output does not match the issue. ### Prompt to paste into your agent ```text In the itsaplan instance at , assign issue to the internal agent and confirm that a run starts. Report the run status and any comment the agent posts on the issue. ``` ### Caveat The README does not describe the exact screens for adding an agent, so confirm the menu path in your instance before writing the agent setup into a runbook. Risk, credentials: The agent gets tools for outside services such as Notion, Telegram, GitHub, and Gitea, so give it only the keys and permissions it needs. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/croffasia-itsaplan/assign-internal-agent-to-team-issues/ ## How to route issues to a coding agent on your own machine with Itsaplan Repo: [croffasia/itsaplan](https://github.com/croffasia/itsaplan) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README Install the runner so your local coding CLI picks up tasks from the tracker. **Who it is for:** A developer who uses Claude Code, Codex, or another coding CLI and wants those tools to take tickets from the team board. **The problem:** Coding tools work in a terminal and do not see the backlog, so each ticket is copied by hand into a prompt. **The outcome:** Tasks assigned to an external agent are handed to your chosen coding CLI on your machine, and the reply streams back to the issue. ### Steps 1. Read the runner setup in docs/runner.md and install the coding CLI you plan to use. 2. Install the runner package `@itsaplan/runner` from the repo's packages/runner folder, following its README. (inferred, check the README) 3. Register the external agent in the instance under your own account and point the runner at it. 4. Assign an issue to the external agent or @mention it in a comment. 5. Check the streamed reply and the coding agent's tool calls on the issue, then review any code changes it made. ### Prompt to paste into your agent ```text Using docs/runner.md in the itsaplan repo, configure @itsaplan/runner for on this machine. Assign issue to the external agent and report whether the reply and tool calls stream back to the issue. ``` ### Caveat The runner is Apache-2.0 while the rest of the repo is AGPL-3.0, so check the license of packages/runner before you embed it in another product. Risk, credentials: The runner works under your own account and the coding CLI can act with your local permissions, so limit what the CLI can reach before assigning it tasks. Risk, remote script: The runner hands each task to a command that reads stdin, so review what that command is allowed to execute on your machine. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/croffasia-itsaplan/run-coding-agent-on-own-machine/ ## How to link pull requests to issues and move them on merge with Itsaplan Repo: [croffasia/itsaplan](https://github.com/croffasia/itsaplan) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Write Fixes KEY-42 in a pull request so the issue follows the code through review. **Who it is for:** A developer or tech lead whose team tracks work in It's a Plan but ships code on GitHub, GitLab, Gitea, Forgejo, or Bitbucket. **The problem:** Issues go stale after the code is merged because nobody updates the tracker by hand. **The outcome:** The pull request is linked to the issue, and the issue moves when the pull request opens and merges. ### Steps 1. Connect your repository's forge to the instance, using GitHub, GitLab, Gitea, Forgejo, or Bitbucket. 2. Find the issue key on the board, for example KEY-42. 3. Write "Fixes KEY-42" in the pull request title or description. 4. Open the pull request and check that it appears on the linked issue. 5. Merge the pull request and confirm the issue moved to the state you expect. ### Prompt to paste into your agent ```text For the itsaplan issue , open a pull request in whose description says "Fixes ". Report whether the pull request is linked to the issue and whether the issue state changes after the pull request opens and after it merges. ``` ### Caveat The README gives the "Fixes KEY-42" pattern as an example only, so test it on one pull request before relying on it across the team. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/croffasia-itsaplan/link-pull-requests-to-issues-automatically/