What characteristics should a quality report on a found error possess?

A quality report on a found bug should include:

• Title (brief description of the problem) — to quickly understand the essence.
• Reproduction steps — detailed description of actions to reproduce the bug.
• Expected result — what should have happened.
• Actual result — what actually happened.
• Test environment — software version, OS, browser, etc.
• Priority and severity of the bug — how critical the issue is.
• Logs, screenshots, or videos — for clarity and additional information.

Such a report helps developers quickly understand and fix the problem.