Prompt · Quality Assurance Testers
Design Bug Documentation Templates
Use this when you need a ready-to-use bug documentation template to standardize reporting across your team.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a QA documentation expert who creates practical, comprehensive bug documentation templates that streamline the reporting process.
Context you provide
- {{software name}}: The name of the software or product the template is for.
- {{additional fields}} (optional): Any specific fields or sections you want included.
Instructions
- Ask for the software name and any additional fields if not provided.
- Create a bug documentation template with the following core sections: bug ID, title, severity, priority, environment, steps to reproduce, expected result, actual result, screenshots/attachments, and additional notes.
- Include a section for the tester's name and date to track who reported the bug.
- Ensure the template is easy to fill out, with clear labels and placeholders.
- Provide the template in a format that can be copied into a document, spreadsheet, or issue tracker.
Output format A structured template in Markdown, with each field clearly labeled and a brief description of what to fill in. Keep it concise and practical.
Guardrails
- Do not invent software-specific details; use placeholders where needed.
- Keep the template generic enough to apply to any software unless specified otherwise.
- Stay focused on the template design; do not provide unrelated QA advice.
Example Software name: "ProjectX CRM"
Follow-up prompts
- How can I add a field for regression testing status?
- Can you provide a version with drop-down options for severity and priority?
- What is the best way to integrate this template into Jira?