Where to report a bug
Bugs belong in GitHub Issues, not this portal. What to include and why.
Report bugs in GitHub Issues
All bugs go to GitHub Issues. Bug Report is the only issue template, so anything else you pick from the "New issue" screen takes you straight to the right place before you start writing.
Please do not post bugs on this feedback portal. Bugs and feature requests need different handling, and mixing them makes both harder to track.
Why bugs live on GitHub
- A bug is closed by the pull request that fixes it. The
Fixes #123keyword only resolves against a live GitHub issue. - Bug reports need logs, versions and reproduction steps, which belong next to the code.
- Keeping only bugs in the Issues tab makes the issue count a real measure of stability rather than a mix of bugs, ideas and questions.
What to include
- PatchMon server version
- How you installed it (Docker, the Proxmox community script, or something else)
- Host operating system and version
- What you expected to happen
- What actually happened
- Steps to reproduce
- Relevant logs, with any secrets or hostnames removed
The more of these you provide, the sooner it gets fixed. Reports without a version and a reproduction usually need a round trip before anyone can start.
What happens after you report it
A new issue carries needs-triage until a maintainer has looked at it. At triage it gets two fields you can read directly on the issue:
Field | Values |
|---|---|
Priority | Urgent, High, Medium, Low |
Effort | High, Medium, Low |
Start and target dates are added when a fix is being aimed at a particular release. Urgent priority skips the queue and can go out in a patch release on its own.
The full development-side flow is in How work gets planned and shipped.
Security vulnerabilities
Do not open a public GitHub issue for a security vulnerability. Report it privately by either:
- Opening a private security advisory
- Emailing support@patchmon.net
Include a description, steps to reproduce or a proof of concept, the affected version or commit, and your disclosure timeline preferences. You will get an acknowledgement within two business days, and we will work with you on a coordinated disclosure.
If you posted something feature-shaped
If a feature request lands in the issue tracker, a maintainer labels it enhancement, moves it to this portal, adds a comment with the direct link, and closes the issue. Nothing you wrote is lost. Follow it here from that point on.
How you find out it is fixed
- The issue is closed by the pull request that fixes it.
- The fix is listed in the Changelog when the release goes out.
Individual bugs do not appear on the public roadmap. Larger reliability work is tracked as themes on the Stability roadmap.
Read next
Was this helpful?
Your feedback shapes what we write next.