← ClaudeAtlas

jira-dashboardlisted

Morning snapshot of Jira tickets (new and recently updated on the tracked projects, plus the user's own open tickets) in a Jira dashboard artifact on claude.ai, refreshed through the Atlassian connector, with a reviewed mark that keeps unreviewed tickets as a backlog and a flag for tickets to discuss. Use whenever the user asks to refresh, update, start or show their Jira dashboard, set up, change or turn off its refresh schedule, mark dashboard tickets reviewed or asks what they haven't reviewed, flags tickets for discussion or asks what's flagged, or asks what's new in Jira or which tickets came in or changed since yesterday; the scheduled refresh task runs it too.
primelogiclabio/claude-jira-dashboard · ★ 0 · AI & Automation · score 72
Install: claude install-skill primelogiclabio/claude-jira-dashboard
# Jira dashboard A claude.ai artifact page that saves the user searching Jira by hand each morning. It has four tabs: - **New Tickets**: tickets created on the tracked projects since the previous refresh day (see Refreshing). - **Recent**: tickets on the tracked projects updated in that same window, leaving out the ones on New Tickets. - **My Tickets**: open tickets assigned to the user, on any project. - **Flagged**: every ticket the user flagged for discussion, with its note, until they unflag it. On New Tickets and Recent the user marks each ticket reviewed. A ticket they haven't reviewed stays on its tab after later refreshes, marked with the day it came in, so nothing slips by. A reviewed ticket drops off at the next refresh, and comes back on Recent if it's updated again. On any tab the user can flag a ticket to bring up with others, with an optional short note. Flags live only in the dashboard's database, never in Jira, and no refresh changes them. The page is built from `template.html` in this skill's folder, a complete HTML page. Its rows aren't in the page's code: they're in the artifact's own database, which the page shows live and Claude writes with the artifact tools (below). A refresh happens three ways, all following the same rules: - the scheduled task runs this skill on the refresh schedule, if the user set one up (there's none by default); - the user asks Claude in chat; - the user presses **Refresh** on the page, or saves the ticket types, and the page