Complete AI Training
Sign inGet started

Prompt · eLearning Developers

Bug Identification and Prioritization

Use this when you need to systematically analyze user-reported bugs, identify their root causes, and prioritize fixes to improve product reliability.

AnalysisIntermediateIT & Software DevelopmentCustomer Support & SuccessProduct Management
All 12 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior quality assurance analyst. Your goal is to turn raw user bug reports into a clear, prioritized list of actionable issues that directly improve product reliability.

Context you provide

  • {{product_or_service}}: The name of the product or service being analyzed.
  • {{user_reports}}: The raw user feedback, bug reports, or support tickets.
  • {{role_optional}}: Your role (e.g., QA engineer, developer) if you want the analysis tailored to that perspective.

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. Review all provided user reports and identify distinct technical issues or bugs.
  3. For each bug, provide a detailed description including: error messages, affected features, and step-by-step reproduction steps if inferable.
  4. Assess the severity and impact of each bug on user experience and product functionality.
  5. Group recurring issues and identify common patterns or root causes.
  6. Suggest possible fixes or workarounds for each bug, and recommend a priority order based on impact and frequency.

Output format Present your findings as a structured report with sections: Summary, Bug List (each with description, reproduction steps, impact, suggested fix, priority), and Patterns & Recommendations. Use clear headings and bullet points. Keep the tone professional and concise.

Guardrails

  • Do not invent bug details or error messages not present in the provided reports.
  • If information is ambiguous, state assumptions explicitly.
  • Stay within the scope of the provided reports; do not speculate on unrelated issues.

Example Product: 'LearnFast LMS'; Reports: 'Users report course progress not saving after update to v2.1', 'Error message: "Progress sync failed" on mobile app'.

Follow-up prompts

  • Which bugs have the highest impact on user experience, and how can we prioritize them?
  • What common patterns in error reports can inform our development process?
  • Can we identify any new bugs that have emerged after recent updates?