Questions and ideas
For questions about how sureops works, discussions about best practices, and feature requests: GitHub Discussions — github.com/sureops-public/sureops/discussions Discussions are the right place for:- “How do I configure X?”
- “What’s the recommended approach for Y?”
- “I’d love a feature that does Z”
- “I’m seeing unexpected behavior — is this by design?”
Bug reports and concrete feature requests
For specific bugs or well-scoped feature requests: GitHub Issues — github.com/sureops-public/sureops/issues/new When filing a bug report, include:- What you expected to happen
- What actually happened
- Steps to reproduce
- Your sureops version or deployment type (cloud / self-hosted)
- Any relevant error messages or screenshots
Documentation improvements
Every page in the sureops docs has an Edit this page link at the bottom (via Mintlify). Clicking it opens the source file on GitHub where you can propose a correction or addition via pull request. For larger documentation gaps — missing pages, inaccurate sections, or topics you’d like covered — open a GitHub Issue with the labeldocs.
Private or account-specific issues
For issues related to your specific account, billing, or anything you don’t want to discuss publicly: Email support@sureops.ai Include your organization name and a description of the issue. For self-hosted deployments, include your Helm chart version and Kubernetes version.What happens to feedback
- Bugs confirmed by the team are triaged, assigned, and fixed in a future release. You’ll see the issue closed with a release reference when it ships.
- Feature requests are reviewed against the roadmap. High-demand requests (many upvotes or +1s) are prioritized.
- Docs improvements from pull requests are reviewed within a few business days and merged when approved.