primelogiclabio/claude-jira-dashboard

A Claude skill that keeps a Jira dashboard on claude.ai: new, recently updated
and your own tickets from your Jira site, refreshed each morning through the
Atlassian connector, with a review mark that keeps unreviewed tickets as a
backlog.
Ask Claude to start one and it publishes the page from
template.html, asks which Jira projects to track, and gives
you the link. It replaces opening Jira and running the same searches by hand
every morning.
Status: early. It works end to end on one setup and is used daily. It
installs from the claude-tools
marketplace (see Install).
## What the page shows
New Tickets: tickets created on the projects you track since the last
morning refresh. On a Monday that reaches back to Friday's.
Recent: tickets on those projects updated in the same window, leaving
out the ones already on New Tickets.
My Tickets: your open tickets, on any project.
Flagged: every ticket you've flagged for discussion, with its note.
Each search tab shows a summary (counts by project and status), the tickets
most recently updated first, and the query it ran.
### Reviewing
On New Tickets and Recent, tick Reviewed once you've looked at a ticket.
A ticket you haven't reviewed stays on its tab after later refreshes, with a
"from Fri" chip showing the day it came in, so nothing slips by. A reviewed
ticket drops off at the next refresh, and comes back on Recent if someone
updates it again. The tab badges count what's left to review, and
Mark all reviewed clears a tab.
### Flagging for discussion
Click the flag next to a ticket's key, on any tab, to keep it on Flagged
for bringing up with others. A note box opens right away so you can say why
(or press Skip), and the note shows under the ticket wherever it appears.
A flag stays until you unflag it, even after the ticket leaves the other tabs.
Each refresh re-reads every flagged ticket, so its status stays current, and
↻ on a Flagged row re-reads just that one. Flags live only in the
dashboard, never in Jira.
Refreshes also re-read the unreviewed tickets they carry over, so a carried
ticket shows its current status, and drops off if it moves into a status the
tab hides or Jira no longer returns it.
### Settings
Projects: which projects New Tickets and Recent search.
Tab settings: for each tab, the ticket types it includes and the
statuses it hides.
Refresh schedule: the days and time of a scheduled refresh, if you want
one, and Turn off scheduled refresh to stop it.
A project menu above each tab's rows shows one project at a time, and an
Auto / Light / Dark switch sets the theme. Each device remembers both.
## How it refreshes
The tickets aren't written into the page. They're records stored with the
artifact on claude.ai, in its own database, and only you (and anyone you make
an Editor) can read them. They're refreshed three ways, all by the same rules:
On a schedule, if you want one: a Claude desktop scheduled task. There's
none by default; Claude sets it up when you ask, and turns it off when you
ask or press Turn off scheduled refresh on the page. It runs while the
desktop app is open; a run missed while the app was closed happens when it
next opens.
When you ask Claude in a Claude Code session ("refresh my Jira