cotera

Jira Sprint Status Reporter

Pull sprint status from Jira automatically. See completion rates, blocked tickets, and overdue issues without opening the board.

Sprint trackingStatus reportsBlocked ticketsTeam visibility

The Challenge

Every standup begins the same way: someone opens Jira, clicks into the sprint board, scrolls through columns, and tries to count what's done versus what's stuck. Filters get applied and removed, swimlanes expand and collapse. By the time you have a clear picture, fifteen minutes have passed and the meeting is half over. The status report your PM asked for? That's another thirty minutes of clicking through individual tickets after the call.

What This Prompt Does

Search Sprint Issues

Uses JQL to pull all issues in the active sprint so you see the full picture at a glance

Group by Status

Categorizes issues into To Do, In Progress, In Review, and Done with counts and percentages

Detect Blockers

Gets full details on at-risk tickets to surface blocked issues, overdue items, and unassigned work

Generate Report

Produces a formatted sprint status with completion percentages, blockers, and action items

The Prompt

The Prompt

Task

Use @Jira/Search IssuesName it "Jira/Search Issues" and call it with @Jira/Search Issues to find all issues in the current sprint using JQL, then use @Jira/Get IssueName it "Jira/Get Issue" and call it with @Jira/Get Issue to get full details on blocked or at-risk tickets. Calculate completion percentages and generate a sprint status summary.

Input

The user provides:

  1. Their Jira project key (e.g., "ENG", "PLAT")
  2. The sprint name or "active sprint" (defaults to current active sprint)
  3. Any additional JQL filters (optional, e.g., specific components or labels)

Example: "Give me the sprint status for the ENG project's active sprint"

Context

Issue Discovery

  1. Use @Jira/Search Issues with JQL: project = [PROJECT] AND sprint in openSprints()
  2. The search returns up to 100 results with summary, status, assignee, and priority
  3. Note the total number of issues returned

Status Grouping

  1. Group issues by their status: To Do, In Progress, In Review, Done
  2. Calculate completion percentage: (Done issues / Total issues) * 100
  3. Track issue counts per status category
  4. Note any issues with High or Highest priority that are not yet In Progress

Blocked & Overdue Detection

  1. Use @Jira/Get IssueName it "Jira/Get Issue" and call it with @Jira/Get Issue on issues that appear blocked or have concerning status patterns
  2. Check the status category field to identify stalled issues (e.g., In Progress for too long)
  3. Review labels for "blocked" or "impediment" tags
  4. Flag High/Highest priority issues without an assignee
  5. Identify issues with due dates that have passed

Sprint Metrics

  • Total issues in the sprint
  • Issues completed vs remaining
  • Completion percentage
  • Number of blocked issues with reasons
  • Number of overdue issues with how many days overdue
  • Unassigned high-priority issues
  • Story points completed vs total (if available from summaries)

Output

Sprint Status Report:

Project: [Project Key] Sprint: [Sprint Name] Overall Completion: [X]%

Status Breakdown:

  • To Do: [count] issues
  • In Progress: [count] issues
  • In Review: [count] issues
  • Done: [count] issues

Blocked Issues:

  • [PROJ-123] [Issue title] - blocked by [reason/dependency]

Overdue Issues:

  • [PROJ-456] [Issue title] - [X] days overdue, assigned to [person]

Unassigned High-Priority Issues:

  • [PROJ-789] [Issue title] - priority: [High/Highest]

Summary: [1-2 sentence overview of sprint health]

Example Usage

Try asking:

  • →"Give me the sprint status for the ENG project active sprint"
  • →"Show completion rates for all issues in Sprint 24 of the PLAT project"
  • →"Find all blocked and overdue issues in the current sprint for MOBILE"