Jira Project Health Auditor

The problem

Jira projects often become cluttered with stale tickets, unassigned work, and broken parent-child relationships that lead to inaccurate sprint metrics. Manually auditing these inconsistencies across hundreds of issues is time-consuming and prone to human error.

What it does

• Identifies 16 specific project health risks including zombie tasks, orphaned issues, and status inconsistencies.
• Fetches real-time data from Jira REST API v2 for any project key or URL.
• Generates a timestamped report folder containing a comprehensive Markdown summary and detailed CSVs for each issue category.
• Automates JQL queries for stale high-priority tasks, sprint overflows, and fix version mismatches.
• Filters issues client-side for complex metrics like heavily discussed but unresolved tickets.

Frameworks & tools

Jira REST API v2, Bash, Python, JQL.

Why this beats prompting it yourself

Writing individual JQL queries for 16 different health checks is tedious. This skill orchestrates the entire workflow, manages local file storage for audit trails, and handles data processing that JQL alone cannot perform, such as comment count filtering.

Use cases

• Run weekly project hygiene audits to clean up the backlog.
• Onboard to a new codebase or project by identifying existing technical debt and blockers.
• Prepare for sprint planning by spotting unpointed tasks or orphaned issues.
• Generate executive summaries of project health for stakeholders.

Known limitations

Requires public access or provided credentials for private instances. Best suited for instances using standard priority and status naming conventions.