📋 Backlog Grooming

Refine a Bug Report Into an Actionable Ticket

Takes a raw bug report from customer support or a user email and rewrites it as a well-structured engineering ticket with repro steps, severity, and impact assessment. Designed for PMs triaging inbound bugs.

This prompt converts unstructured bug reports into engineering-ready tickets using a Repro-Expected-Actual-Severity-Impact template. It adds a 1-5 severity score based on customer count, revenue exposure, and workaround availability.

When to use this prompt

Use this every time a support ticket, email, or Slack message lands with a vague bug description. You will paste in the raw report and any context you have about the affected customers. The prompt assumes you know roughly how to classify severity (P0-P4) in your org; if you have a written severity rubric, paste it into the context block for best results. It is particularly useful when the original reporter is not technical and the report is missing the structured fields engineers need to reproduce and fix the issue quickly.

The Prompt

Role: Product Manager Variables: {{raw_report}}, {{reporter}}, {{affected_customers}}, {{product_area}}, {{severity_rubric}} 
You are a product manager triaging an inbound bug. Rewrite the raw report below into a clean engineering ticket using this exact structure.

Raw report:
{{raw_report}}

Reporter: {{reporter}}
Affected customers: {{affected_customers}}
Product area: {{product_area}}
Severity rubric: {{severity_rubric}}

Structured ticket output:

1. TITLE — One line, specific, action-oriented (e.g., "Checkout fails when discount code is applied twice"). Max 80 characters.

2. SUMMARY — 2-3 sentences describing what broke and where.

3. STEPS TO REPRODUCE — Numbered list. If steps are missing from the raw report, list the minimum 3 questions the reporter must answer before this ticket can be worked on.

4. EXPECTED BEHAVIOR — What should happen.

5. ACTUAL BEHAVIOR — What happens instead. Include error messages verbatim.

6. ENVIRONMENT — Browser, OS, app version, user role if known. Mark each field UNKNOWN if not in the report.

7. SEVERITY — P0 to P4, with a 1-sentence justification referencing the rubric.

8. CUSTOMER IMPACT — Number of affected customers, revenue exposure if known, whether a workaround exists.

9. SUGGESTED OWNER — Team or role (not a person).

If the raw report is too vague to fill any required field, write "BLOCKED: Need [specific info] from reporter" instead of guessing.

Example Output

TITLE: Invoice PDF export fails silently for users on Safari 17

SUMMARY: When Safari 17 users click Export PDF on the invoice page, the download spinner shows briefly then disappears with no error and no file. Chrome and Firefox users are unaffected.

STEPS TO REPRODUCE:
1. Log in as customer admin on Safari 17.
2. Navigate to Billing > Invoices.
3. Click Export PDF on any invoice.
4. Observe spinner then nothing happens.

EXPECTED: PDF downloads to default folder.
ACTUAL: Spinner for ~800ms, no download, no error toast, no network request in dev tools.

ENVIRONMENT: Safari 17.2, macOS 14.3, customer admin role, app v4.18.

SEVERITY: P2. Blocks a core billing workflow for a single browser but a workaround (use Chrome) exists.

CUSTOMER IMPACT: 4 customers reported, est. 12 percent of billing admins use Safari. Revenue exposure: none directly, but trust impact on finance users.

SUGGESTED OWNER: Billing team.

Recommended Tools

Linear and Jira both have bug-specific issue templates with fields that map one-to-one onto the output structure, so you can paste sections directly. ClickUp has the best customer-field linking when the bug came from a support ticket in Zendesk or Intercom. All three let you tag severity as a property for filtering in sprint reviews.

Linear74/100 Jira Software75/100 ClickUp94/100

Related Prompts

Identify Duplicates and Stale Backlog Items

Audits a backlog of 30+ items and flags duplicates, near-duplicates, and items that have gone stale based on age and activity. Built for PMs inheriting or cleaning up a bloated backlog.

Product Manager

Translate Support Themes Into Backlog Items

Clusters repeat customer support tickets into 5-8 underlying product themes and converts each into a backlog item with impact data. Built for PMs who need to turn a noisy support queue into a clear signal.

Product Manager

Draft a One-Page PRD From a Problem Statement

Turns a brief problem statement into a one-page PRD with problem, solution, success metrics, and rollout plan. Built for PMs who need a lightweight PRD format for small-to-medium features.

Product Manager

Frequently Asked Questions

When should I use this prompt?

Use it within minutes of receiving any bug report that is not already in your team's structured format. The faster you convert unstructured reports into proper tickets, the less context is lost between the reporter and the engineer. If your support team uses a shared triage queue with pre-filled templates, you may not need it. But if bugs arrive as Slack messages, emails, or customer calls, this prompt pays back every use by saving the engineer a context-gathering round-trip.

What if the reporter is not reachable to fill gaps?

Mark every missing field UNKNOWN in the environment section and list the BLOCKED items explicitly. Do not make up repro steps; engineers waste cycles chasing phantom bugs when PMs guess. Instead, attempt repro yourself with the information you have, add your own findings as a comment, and then either close-as-needs-info or escalate to a tier-2 support person who can contact the original customer. Never promote a BLOCKED ticket to a sprint.