NexQloud Knowledge Base
Discover tailored support solutions designed to help you succeed with NexQloud, no matter your question or challenge.

How do I submit bug reports or technical issues?
NexQloud's bug reporting system is designed to facilitate rapid issue identification, reproduction, and resolution while maintaining the transparency that defines our community-driven approach. Our structured reporting process ensures that technical issues receive appropriate attention based on severity and impact while providing clear communication throughout the resolution process. This systematic approach reflects our commitment to platform reliability and developer success.
The bug reporting workflow is integrated with our development processes to ensure seamless transition from issue identification to resolution implementation. Reporters receive regular updates on progress and can contribute to validation of proposed solutions.
Bug Report Categories:
- Critical Issues: Platform stability problems, security vulnerabilities, and data integrity concerns with [Information Needed - critical issue response times and escalation procedures]
- Functional Bugs: Feature malfunctions, integration problems, and performance degradation with [Information Needed - functional bug processing timeline and resolution procedures]
- Documentation Issues: Inaccurate or outdated documentation, missing information, and [Information Needed - documentation update process and timeline]
- Enhancement Requests: Minor improvements and optimization suggestions with [Information Needed - enhancement evaluation and implementation process]
Submission Requirements:
Bug reports must include comprehensive information such as [Information Needed - specific required information, reproduction steps, and environment details] to enable efficient reproduction and resolution. Templates are provided to ensure consistent, actionable reporting.
Resolution Communication:
Reporters receive regular updates through [Information Needed - communication channels and update frequency], including estimated resolution timelines and opportunities to validate proposed solutions before general release.

.webp)





.webp)
.webp)
.webp)
.webp)

.webp)
.webp)






