QA Issues Tracker

Overview

The QA Issues page lets administrators and QA team members report bugs, request changes, and track platform improvements. Issues can be prioritized, filtered by status, and updated inline - creating a simple workflow for managing quality and change requests.

Accessing QA Issues

1. Log in with an admin account
2. Navigate to /admin/qa/issues
3. View the issues list with status, priority, and reporter

Creating an Issue

Adding a New Issue

1. Click "New Issue" button
2. Fill in the form:
   • Title: Short summary of the bug or request
   • Description: Detailed explanation of the issue
   • Priority: LOW, MEDIUM, HIGH, or CRITICAL
   • Page: Optional - where the issue occurs (e.g., /admin/qa/issues)
   • Screenshot: Optional - URL to a screenshot showing the issue
3. Click "Submit"
4. The issue appears in the list with "Open" status

Issue Statuses

• Open: New issue that hasn't been started
• In Progress: Someone is actively working on it
• Done: Issue resolved and deployed
• Won't Fix: Decided not to address this issue

Managing Issues

Filtering Issues

1. Use the status dropdown above the list
2. Select a status to filter (or "ALL" to see everything)
3. Issues update automatically

Updating Status or Priority

1. Find the issue in the list
2. Click the status badge or priority badge
3. Select a new value from the dropdown
4. Change saves automatically

Deleting an Issue

1. Click the trash icon next to an issue
2. Confirm deletion in the dialog
3. Issue is permanently removed

Issue Details

Each issue shows:

• Title and description - What the issue is
• Priority badge - Color-coded by severity (gray=LOW, blue=MEDIUM, orange=HIGH, red=CRITICAL)
• Status badge - Current state with icon (amber=Open, blue=In Progress, green=Done, gray=Won't Fix)
• Page location - Where the issue occurs (if provided)
• Screenshot link - Visual reference (if provided)
• Reporter email - Who created the issue
• Created date - When it was reported

Tips

• Use CRITICAL priority for issues that break core functionality or prevent users from working
• Add page URLs to help developers locate the issue quickly
• Include screenshots for UI bugs - upload to Imgur or similar and paste the link
• Write clear descriptions - include steps to reproduce for bugs, or user stories for change requests

Questions

Q: Who can access the QA Issues page? A: Any admin user can view and manage issues. The page is located under Admin > QA > Issues.

Q: Can I attach files directly to issues? A: Not yet - use the screenshot URL field to link to images hosted elsewhere (Imgur, Dropbox, etc.).

Q: How do I know when an issue is fixed? A: Watch for the status to change to "Done". The issue will remain visible in the list for reference.