Jira Sprint Status Reporter
Pull sprint status from Jira automatically. See completion rates, blocked tickets, and overdue issues without opening the board.
Free to start
1,000 credits included
No credit card required
Try this agent Book a demoSetup in 5 min · Cancel anytime
Setup time
~5 min
Time saved
30 min/standup
Difficulty
Easy
Tools
1 connected
How it works
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
Try asking
View the agent prompt
See the full instructions this agent runs on — copy, edit, or customize it
ExpandCollapse
View the agent prompt
See the full instructions this agent runs on — copy, edit, or customize it
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:
- Their Jira project key (e.g., "ENG", "PLAT")
- The sprint name or "active sprint" (defaults to current active sprint)
- 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
- Use @Jira/Search Issues with JQL:
project = [PROJECT] AND sprint in openSprints() - The search returns up to 100 results with summary, status, assignee, and priority
- Note the total number of issues returned
Status Grouping
- Group issues by their status: To Do, In Progress, In Review, Done
- Calculate completion percentage: (Done issues / Total issues) * 100
- Track issue counts per status category
- Note any issues with High or Highest priority that are not yet In Progress
Blocked & Overdue Detection
- 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
- Check the status category field to identify stalled issues (e.g., In Progress for too long)
- Review labels for "blocked" or "impediment" tags
- Flag High/Highest priority issues without an assignee
- 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]
WHAT ARE YOU WAITING FOR?
Ready to build?
Stop duct-taping tools.
Stop writing playbooks no one follows.
Start building agents that actually do the work—and do it well.
Cotera: For people who think busywork is boring.
"This is the best product ever when it comes to shipping. Ten on ten recommended. I just can't wait to see what happens with this product."
Rebecca Blount
Director, Customer Success