Account Management

Submitting Bug Reports and Feature Requests

8 views Updated 2 days ago

WebMon's bug reporting system allows you to report issues, request new features, and track the progress of your submissions.

Types of Reports

  • Bug: Something isn't working correctly
  • Feature Request: A new capability you'd like to see
  • Improvement: Enhancement to an existing feature
  • Question: General questions about functionality

Submitting a Report

  1. Click your name in the navigation
  2. Select "Bug Reports" from the dropdown
  3. Click "Report a Bug"
  4. Fill out the form:
    • Title: Brief description of the issue
    • Type: Select the appropriate category
    • Description: Detailed explanation
    • URL: (optional) If the issue is on a specific page
    • Steps to Reproduce: How to trigger the issue
    • Expected Behavior: What should happen
    • Actual Behavior: What actually happens
    • Screenshots: Attach up to 3 images (optional)
  5. Click "Submit Report"

Tracking Your Reports

Your bug reports are organized into three tabs:

Active Tab

  • Open: New reports awaiting review
  • In Progress: Reports being worked on

Resolved Tab

  • Issues that have been fixed
  • Shows resolution date

Closed Tab

  • Reports closed without action
  • Duplicate or invalid submissions

Getting Updates

When there's activity on your report, you'll see:

  • Email notification about the update
  • "Update" badge on the bug in your list
  • Blue highlight on rows with unread updates

Click on any report to view its full history and any responses from our team.

Replying to Reports

You can add additional information to your reports:

  1. Open the bug report
  2. Scroll to the reply section
  3. Add your message (10-2000 characters)
  4. Click "Send Reply"

Note: You can send up to 5 replies per day per report.

Closing Your Reports

If your issue is resolved or no longer relevant:

  1. Open the bug report
  2. Click "Close Ticket"
  3. The report moves to the Closed tab

Report Priorities

Our team assigns priority levels:

  • Critical: Major functionality broken
  • High: Significant impact on users
  • Medium: Moderate impact, workaround exists
  • Low: Minor issues or cosmetic problems

The priority determines the order in which reports are addressed.