Skip to content

How to Report a Bug

Found a bug in Reservium? Your reports help us make the system more stable and reliable for everyone. Thank you for taking the time to let us know!

Before Submitting

To help us fix the issue quickly, please take a moment to:

  • Check existing issues: Search our GitHub Issues to see if the bug has already been reported.
  • Update to latest: Ensure you are using the latest version of Reservium.
  • Isolate the problem: Try to reproduce the bug in a clean environment to rule out local configuration issues.

How to Submit

We use GitHub Issues to track all bug reports. This ensures that the technical details are captured and tracked until resolved.

Steps to Submit:

  1. Navigate to the Reservium API Repository.
  2. Click on the Issues tab.
  3. Click the New Issue button.
  4. Select the Bug Report template (if available) or start a blank issue.

What to Include:

A Good Bug Report Includes...

  • Descriptive Title: A clear, concise summary of the issue.
  • Steps to Reproduce: Detailed instructions on how to trigger the bug.
  • Expected Behavior: What you expected to happen.
  • Actual Behavior: What actually happened (include error messages).
  • Environment Details: Browser version, OS, and Reservium version.
  • Logs & Media: Attach screenshots, videos, or relevant log snippets.

What Happens Next?

Once you submit your report, here is what you can expect:

  1. Validation: Our team will attempt to reproduce the bug using the steps you provided.
  2. Clarification: If we need more information (like logs or specific settings), we'll ask follow-up questions in the issue.
  3. Resolution:
    • Confirmed: If the bug is confirmed, we'll label it and add it to our development backlog.
    • Fixed: Once a fix is merged, the issue will be updated and closed.
    • Not a Bug: If the behavior is intended or due to configuration, we'll explain why and help you troubleshoot.

Tips for Success

  • One Bug per Issue: If you found multiple problems, please open a separate issue for each one.
  • Be Clear and Concise: Avoid vague descriptions like "it doesn't work."
  • Include Logs: Error logs from the browser console or the backend are often the fastest way to find a fix.

Ready to Report?

Head over to GitHub and help us improve Reservium!