Dashboard Jira — AI skill for Claude Code

Dashboard Jira

A local control tower for running several [Claude Code](https://claude.com/claude-code) sessions on a Jira backlog. It reads Jira, turns new and returned tickets into cards, and lets you decide from your desktop or your phone which AI session works on each one.


Why

When several AI coding sessions work in parallel (one per product area), someone has to watch Jira, decide what goes where, pass each session the ticket and its attachments, and collect the answers. Dashboard Jira does that plumbing. You keep the decisions: nothing is sent to a session until you approve it.

How it works

1. A reporter session reads Jira every few minutes. It publishes a short report and creates a card for each new ticket, each ticket returned from review and each new comment on one of your tickets.
2. You approve cards on the board, from the browser or from your phone. Each card goes to the session that owns its epic.
3. An orchestrator session delivers the approved work, with the ticket's attachments already downloaded. Each session reports back done, partial or question, and you answer from the board.

It also has:

• one-click deploy orders;
• a chat with the sessions (voice notes transcribed locally with Whisper; replies spoken with Piper);
• push notifications;
• an hourly activity summary of a colleague;
• a "Learning" tab that tracks how often work comes back from review.

Everything runs on your machine: a Node server on `127.0.0.1`, a SQLite file and your Jira API token in a local `.env`. Nothing is sent anywhere other than your own Jira. The interface is in Spanish.

Quick start

git clone https://github.com/Albrodpul/dashboard-jira.git
node dashboard-jira/install.js C:/work/acme/board   # create