Operate with confidence
Pick the right support lane before you open the tab.
Support works faster when the report starts in the right place. Use this page to decide where to ask for help and what details you need to bring with you.
Bug
Use this lane for runtime or product failures you can reproduce.
Docs
Use this when the product is fine but the guidance is wrong or missing.
Feature
Use this when you are asking for a new capability instead of reporting a defect.
Security
Never put vulnerabilities in a public issue thread.
Before opening an issue
Check the obvious pages first.
Bring these details
- whether you are using Tiny mode or self-hosted mode
- version or commit
- install method
- exact repro steps
Contact lanes
Use the lane that matches the problem.
| Lane | Use it for | Where to go |
|---|---|---|
| Public bug/docs/feature issue | Reproducible product bugs, docs fixes, and feature requests that belong in public | GitHub Issues |
| Private coordination | Questions that do not belong in a public issue thread or need direct coordination first | support@urgentry.com |
| Security | Vulnerabilities, exploit reports, and anything that should stay private until fixed | Security policy |
Issue type
Open the issue that matches the problem.
Bug report
Use this for runtime or product failures you can reproduce.
Docs report
Use this when the docs are wrong, stale, or missing a key step.
Feature request
Use this when you are proposing a new capability instead of reporting a defect.
Security
Do not report vulnerabilities in public issues. Use the security policy instead.
Need the right contact?
Use the security lane for vulnerabilities. Use GitHub issues for bugs, docs fixes, and feature requests that belong in public.