Linear Bug Tracker
Track bugs across Linear projects. Find unassigned high-priority bugs, generate severity reports, and flag aging issues.
The Challenge
Bugs accumulate across projects and teams faster than anyone can track them. Some are urgent but sitting unassigned. Others have been open for months with no progress. When leadership asks "how many open bugs do we have?" nobody can answer without spending an hour filtering through Linear views and cross-referencing priorities. The critical ones get lost in the noise.
What This Prompt Does
Find All Bugs
Searches for issues labeled as bugs and those with bug-related keywords across your team
Check Details
Fetches full details to verify priority, assignee, age, and cycle assignment for each bug
Flag Critical Issues
Identifies high-priority bugs without assignees, stale bugs, and those blocking other work
Generate Report
Produces a severity report grouped by priority and age with actionable alerts
The Prompt
The Prompt
Task
Use @Linear/List IssuesName it "Linear/List Issues" and call it with @Linear/List Issues to search for issues labeled "bug" or with bug-related keywords. Use @Linear/Fetch IssueName it "Linear/Fetch Issue" and call it with @Linear/Fetch Issue to get full details. Check if bugs have a priority and assignee. Use @Linear/Update IssueName it "Linear/Update Issue" and call it with @Linear/Update Issue to flag issues and @Linear/Add LabelName it "Linear/Add Label" and call it with @Linear/Add Label to tag them. Generate a bug status report grouped by severity and age.
Input
The user provides:
- Their Linear team name or ID (or "all teams")
- Time range for the report (optional, defaults to all open bugs)
- Any specific filters (e.g., only a project, only unassigned bugs)
Example: "Show me all open bugs for the Backend team, grouped by priority"
Context
Bug Discovery
- Use @Linear/List IssuesName it "Linear/List Issues" and call it with @Linear/List Issues to find issues with the "bug" label
- Also search for issues containing bug-related keywords in the title: "crash", "error", "broken", "fix", "regression"
- Filter to only open issues (not Done or Cancelled)
- Combine and deduplicate results
Bug Detail Analysis
- Use @Linear/Fetch IssueName it "Linear/Fetch Issue" and call it with @Linear/Fetch Issue to get full details on each bug
- Check for the following attributes:
- Priority: Is it set? What level?
- Assignee: Is someone working on it?
- Due date: Is it overdue?
- Created date: How old is the bug?
- Labels: Are they properly categorized?
- Cycle: Is it scheduled in a sprint?
Critical Bug Detection
- Flag bugs with Urgent or High priority that have no assignee
- Flag bugs older than 14 days with no state change
- Flag bugs with no priority set at all
- Identify bugs that are blocking other issues
Bug Metrics
- Total open bugs across teams
- Bugs by priority (Urgent, High, Medium, Low, No Priority)
- Bugs by age (< 7 days, 7-14 days, 14-30 days, > 30 days)
- Unassigned bugs by priority
- Bugs without a cycle/sprint assignment
Output
Bug Status Report:
Team: [Team Name] Total Open Bugs: [count] Report Date: [date]
Priority Breakdown:
- Urgent: [count] bugs
- High: [count] bugs
- Medium: [count] bugs
- Low: [count] bugs
- No Priority: [count] bugs
Age Distribution:
- Less than 7 days: [count] bugs
- 7-14 days: [count] bugs
- 14-30 days: [count] bugs
- Over 30 days: [count] bugs
Critical Alerts:
- [Issue ID] [Title] - Urgent priority, no assignee, [X] days old
- [Issue ID] [Title] - High priority, stale for [X] days
Unassigned High-Priority Bugs:
- [Issue ID] [Title] - [priority], created [date]
Aging Bugs (> 30 days):
- [Issue ID] [Title] - [priority], assigned to [person], [X] days old
Summary: [1-2 sentence overview of bug health and recommended actions]
Example Usage
Try asking:
- →"Show me all open bugs for the Backend team, grouped by priority"
- →"Find unassigned high-priority bugs across all teams"
- →"Generate a bug aging report for bugs older than 2 weeks"