Submit after signing in
The ticket passes session and CSRF checks, persists in PostgreSQL, returns a unique ID, and enters the admin workflow.
Account-scoped trackingFEEDBACK / TWO CHANNELS
Send each problem somewhere it will actually be handled
Signed-in users can submit directly to the website back office, while public discussions can continue in GitHub Issues.
Two channels with explicit boundaries
Both the website ticket and GitHub Issues are real destinations, never placeholder forms.
Public Issues
Use this channel for problems that can be reproduced, discussed, and collaborated on in public. A GitHub account is required.
Public collaborationPrepare the smallest reproducible report
Clear context is more useful and safer than a complete log dump.
Platform and version
Identify Windows, Linux, Android, macOS, iOS, Cloud, or agent and provide the actual application version.
Do not guess the versionExpected and actual results
Describe the shortest reproduction path, then separate what you expected from what actually happened.
Make it reproducibleSubmit redacted text only
Never include passwords, private keys, tokens, real host addresses, cookies, or full sensitive logs. Attachments are not accepted yet.
Sensitive content is rejected or redacted