Good tickets read like a respectful briefing, not a novel. Lead with the user-visible symptom, then list what you already ruled out in the order you ruled it out. That order matters because escalation teams infer your thinking from it.
Avoid brand cheerleading or blame; stick to observable facts. If you rebooted once, say so. If logs are clean, say which filter you used. Screenshots help, but annotate them lightly so a mobile reviewer understands the arrow without audio.
When you hand off across time zones, add a single line about user impact in plain language. Not priority jargon—impact. Close with the next action you would take if you had thirty more minutes. That line keeps continuity honest without pretending you solved everything.