# Linear Sprint Status Reporter

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

Source: https://cotera.co/solutions/ops/linear-sprint-status-reporter

---

- **Team:** Operations
- **Tools:** Linear
- **Difficulty:** easy
- **Setup time:** 5 min
- **Time saved:** 30 min/standup

## How it works
1. **List Issues** — Pulls all issues in the current cycle for your team so you can see the full sprint at a glance
2. **Group by State** — Categorizes issues into backlog, todo, in progress, in review, and done with counts and percentages
3. **Find Blockers** — Identifies blocked issues, overdue tickets, and unassigned high-priority work that needs attention
4. **Generate Report** — Produces a formatted sprint status with completion percentages, blockers, and action items

## Example requests
- Give me the sprint status for the Platform team's current cycle
- Show completion rates for all issues in the Q1 Release cycle
- Find all blocked and overdue issues for the Mobile team

## Prompt

```markdown
## Task

Use @Linear/List Issues to pull issues in the current cycle/sprint filtered by team, then group by state (backlog, todo, in progress, done). Use @Linear/Fetch Issue to get details on blocked or overdue issues. Calculate completion percentages and generate a sprint status summary.

## Input

The user provides:
1. Their Linear team name or ID
2. The cycle or sprint to report on (optional, defaults to the current active cycle)
3. Any specific filters (e.g., only a particular project or label)

**Example:** "Give me the sprint status for the Platform team's current cycle"

## Context

### Issue Discovery

1. Use @Linear/List Issues filtered by the specified team and current cycle
2. If no cycle is specified, use the active cycle for the team
3. Note the total number of issues returned

### State Grouping

1. Group issues by their state: Backlog, Todo, In Progress, In Review, Done, Cancelled
2. Calculate completion percentage: (Done + Cancelled issues / Total issues) * 100
3. Track issue counts per state category
4. Note any issues with high priority (Urgent or High) that are not yet in progress

### Blocked & Overdue Detection

1. Use @Linear/Fetch Issue on issues that appear blocked or have sub-issues
2. Check for issues with a due date that has passed and are not in a completed state
3. Flag Urgent or High priority issues without an assignee
4. Identify issues that have been in "In Progress" for an unusually long time relative to their estimate

### Sprint Metrics

- Total issues in the cycle
- 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
- Points completed vs total (if estimates are used)

## Output

**Sprint Status Report:**

**Team:** [Team Name]
**Cycle:** [Cycle Name / Date Range]
**Overall Completion:** [X]%

**State Breakdown:**
- Backlog: [count] issues
- Todo: [count] issues
- In Progress: [count] issues
- In Review: [count] issues
- Done: [count] issues

**Blocked Issues:**
- [Issue ID] [Issue title] - blocked by [reason/dependency]

**Overdue Issues:**
- [Issue ID] [Issue title] - [X] days overdue, assigned to [person]

**Unassigned High-Priority Issues:**
- [Issue ID] [Issue title] - priority: [Urgent/High]

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

## Related reading
- [Linear vs Jira: We Migrated 2,000 Issues. Here's What Happened.](https://cotera.co/articles/linear-vs-clickup-comparison.md)