How to Explain a Problem Using Screenshots?
Let images and text complement each other to avoid treating unseen details as facts.
What Are Screenshots Suitable For?
Screenshots are suitable for showing page layouts, error messages, tool interfaces, or visible states. They help illustrate what you see but cannot directly provide the underlying requests, complete source code, or hidden fields behind the page. When preparing screenshots, try to keep titles, buttons, and prompt texts related to the issue so viewers know which step's result it is.
Include the Process of Occurrence
When the attachment option is available, add screenshots and explain "what I did, what I expected, and what I actually saw." For text-heavy errors, also paste key error texts to avoid relying solely on image recognition. Before sending, obscure tokens, personal information, and other unrelated windows.
- Select clear screenshots and check for sensitive information.
- Explain which step the screenshot is from and which areas need attention.
- Request answers to separately describe visible phenomena and possible causes.
How to Review Answers
First verify whether the answer accurately reads the content in the image, then see its explanation of the cause. If the text is very small or the screenshot is incomplete, supplement with partial screenshots and original text. Speculations from image analysis do not equal a reproduced problem; if actual verification is needed, provide operation records separately or clearly arrange available tools to perform checks. If focusing on a certain button, write its name and position in the text.