What makes a technical problem report useful to another person?

Include a clear title, environment, expected and actual results, minimal reproduction steps, frequency, and impact. Attach relevant sanitized logs or screenshots and describe what you already tested. Distinguish direct observations from hypotheses. A small reproducible example is often more useful than a large unexplained code dump. Remove passwords, personal data, and access tokens before sharing. If the issue cannot be reproduced, provide timestamps and correlation identifiers that help locate evidence without implying that an unverified theory is the established cause.