Start with a specific title
Describe what failed, where it happened and the condition that triggered it. Avoid vague titles such as “button broken”.
Use reproducible steps
Write the minimum numbered actions needed to trigger the problem. Include test data, permissions and environment details where relevant.
Separate actual and expected results
The actual result explains what happened. The expected result explains the intended behaviour.
Add useful evidence
Screenshots, recordings, request data, logs and database evidence can make a defect far easier to understand.
Explain the impact
Severity should reflect the impact on the user and system. Priority should reflect how urgently the business needs the issue fixed.