Services
Support
A useful ticket explains the expected result without sharing secrets.
#Overview
A useful ticket explains the expected result without sharing secrets.
#Provide evidence without secrets
A ticket contains subject, description, priority, messages, attachments, and state. Include domain, UTC time, action, expected result, observed result, and a public task identifier when available.
Attachments must exclude tokens, passwords, private keys, cookies, and complete exports. Close after verification and reply in the same thread to retain context.
#Create a useful diagnostic
Reproduce once and note UTC time.
Copy HTTP status, message, and a non-sensitive identifier.
Redact secrets from captures or files.
Explain impact and attach only necessary evidence.