Turn a Customer Bug Report into an Engineering Ticket

Converts messy customer bug reports into a structured engineering ticket with repro steps, environment details, and severity justification.

Prompt

Prompt
Act as a senior technical support engineer triaging a customer bug report for the product engineering team.

I will paste the customer's message, chat transcript, or support ticket below. Turn it into a clean, actionable engineering bug ticket.

Rules:
- Do not invent environment details, error codes, or steps the customer did not mention; mark missing details as "Not provided".
- Write reproduction steps as a numbered list where each step is a single, concrete user action.
- Separate observed facts from customer guesses about the root cause.
- Assign a severity level (Critical, High, Medium, or Low) based on user impact and workaround availability, and justify it in one sentence.

Output format:## Ticket Summary
One-line title starting with the affected feature.

## Environment
Bullet list of OS, browser, app version, and account tier (or "Not provided").

## Reproduction Steps
Numbered list of exact actions.

## Expected vs. Actual Behavior
- **Expected:** What should happen.
- **Actual:** What happened instead, including any exact error text.

## Severity & Justification
Level and one-sentence reason.

## Missing Information
List any gaps support should ask the customer about before engineering picks this up.

Example output

At a glanceRepro steps for the CSV export bugExport with a custom date filter returns Error 500
  1. Log in to Enterprise workspaceStep 1Workspace needs at least 500 tasks
  2. Open project board in List ViewStep 2Switch from the main project board
  3. Apply custom date range filterStep 3For example Jan 1 to March 31
  4. Export as CSVStep 4Red banner shows Export failed (Error 500)

Example for: a B2B project management SaaS support team escalating a CSV export failure reported by an Enterprise customer.

Ticket Summary

CSV Export: Downloading project task list with custom date filters returns a 500 error

Environment

  • OS: macOS 14.4
  • Browser: Chrome 124
  • App Version: Web app (build not provided)
  • Account Tier: Enterprise

Reproduction Steps

  1. Log in to an Enterprise workspace with at least 500 tasks.
  2. Open the main project board and switch to List View.
  3. Apply a custom date range filter (e.g., Jan 1 to March 31).
  4. Click the Export button in the top-right toolbar and select "CSV".

Expected vs. Actual Behavior

  • Expected: A CSV file containing the filtered tasks downloads to the user's computer.
  • Actual: A red banner appears saying "Export failed (Error 500)" and no file downloads. Exporting without the date filter works normally.

Severity & Justification

High — A core reporting workflow is broken for Enterprise accounts, though users can work around it by exporting all tasks and filtering manually in Excel.

Missing Information

  • Exact workspace ID and affected project ID.
  • Whether the issue reproduces in an incognito window or another browser.
  • Approximate number of tasks matched by the date filter.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Prevents engineers from wasting time by separating customer guesses from observed facts.
  • Forces single-action numbered repro steps and flags missing environment data upfront.
  • Requires a one-sentence severity justification tied directly to impact and workarounds.

Paste the customer's email, chat log, or ticket notes right after the prompt in Gemini, ChatGPT, or Claude before escalating to engineering.

Common edits

  • Add your team's exact severity definitions (P0–P3) in the rules so the label matches your Jira setup.
  • Ask for a 2-sentence customer-facing holding reply at the bottom if you still need to gather missing info.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Customer Support