A screenshot can show a disabled button, a misplaced label, or the final state of a failed task. It cannot tell a developer every step that led there. A useful bug report combines a focused image with a short written account of what you did, what you expected, and what happened instead. Use the lightingshot editor to make the image support that account.

You can import an existing screenshot without installing the capture extension. The steps below use the current Chinese interface labels, with their English meanings alongside them. They describe preparing an attachment, not automatically diagnosing a bug or sending a report.

Choose the state that demonstrates the problem

Capture the screen after the unexpected result appears. Keep the relevant control, its label, and enough surrounding interface to identify the task. For a save failure, that might mean the edited field, the Save button, and the visible error message. A picture of the entire desktop often makes this evidence smaller without adding useful context.

Use a separate image for a separate state when a before-and-after comparison matters. This editor does not assemble two images side by side or retain multiple imported documents. Importing another file replaces the current canvas and edit history, so export the first attachment before starting the next.

Prepare the attachment in five steps

  1. Import the screenshot. Choose 导入图片 (Import image) and select your local file. Check that you have the intended state rather than the editor's sample image.
  2. Keep a useful frame. Select 裁剪 (Crop) and drag around the failing area with its identifying context. Release to apply. Avoid removing a field label or error message that explains the result. Use Undo if the frame is too tight.
  3. Cover unrelated private details. Use 遮盖 (Cover) for account names, addresses, or tokens that are not necessary for reproduction. Review repeated details elsewhere in the image. A highlight is translucent and is not a privacy cover.
  4. Point to one primary observation. Select 箭头 (Arrow) and drag toward the failing control. Place the arrow where it does not obscure text. Add a short 文字 (Text) label such as “Save stays disabled” rather than a paragraph of reproduction steps.
  5. Export and inspect. Choose 导出图片 (Export image), select PNG as a starting format for interface text, and use 下载文件 ↓ (Download file). Open the result and check the smallest detail a developer will need.

Pair the image with a reproducible written example

Keep the written report outside the screenshot so its steps can be copied, searched, and corrected. Replace the following illustrative details with your real observation; they are an example structure, not a test we performed.

Task: Update a profile display name
Environment: Your browser version and operating system
Steps: Open Profile → change Display name → select Save
Expected: The new display name is saved
Actual: Save remains disabled after the field is changed
Attachment: profile-save-disabled.png

If the problem is intermittent, say so and describe the attempts you actually made. Do not turn one failed attempt into a claim that a feature never works. Avoid putting passwords, session tokens, or private customer records into the steps merely because they appeared during the failure.

Make annotations observations, not diagnoses

“The total shows 0 after adding two items” is more useful than “The database is broken.” The first label identifies visible evidence; the second proposes an unverified cause. Use one numbered label per observation only when the report needs several references. Lightingshot adds labels individually and does not generate automatic numbered callouts.

The current editor cannot move or restyle an existing text object. If a label covers evidence, use 撤销 (Undo) and add it again. Crop before annotating when practical. Editing zoom changes the display size, not the pixels in the downloaded file.

Do a final attachment check

Read the report once without the image, then inspect the image without your explanation. Together they should identify the task and the unexpected state without forcing the recipient to guess. Confirm that the exported attachment is the covered copy, not the sensitive original. Keep the original separately if your workflow requires it.

For tool details, see arrows and text labels. Use the privacy-cover checklist before sharing, and the crop guide when the relevant control is lost inside a large capture.