QA & Bug Tracking

Built-in bug tracker with kanban board, email-in reports, AI auto-triage, and full integration with messaging and helpdesk.

On this page

Bug Lifecycle

Every bug follows a status workflow:

new → triaged → fixing → testing → closed
  |         |          |           |
  v         v          v           v
duplicate  wont_fix  need_info  reopened
  • new — Just reported, no one has looked at it
  • triaged — Reviewed, priority set, assigned
  • fixing — Developer is working on it
  • testing — Fix ready, awaiting verification
  • closed — Verified and done
  • need_info — Waiting for more details from reporter
  • reopened — Fix didn't work, back to developer

Reporting Bugs

Bugs can be created from multiple sources:

Console form

QA → Report Bug — full form with title, description, priority, screenshots, labels.

Email

Send email to your QA mailbox (e.g. bugs@company.com). Subject becomes title, body becomes description, attachments become screenshots.

From message

Right-click any Disqua message → "Create Bug Report". Content and attachments are carried over.

From helpdesk ticket

On ticket detail → "Create Bug from Ticket". Bug and ticket are automatically linked.

Kanban Board

The board view shows bugs as cards in columns by status. Drag and drop cards between columns to change status. Each card shows bug number, title, priority dot, assignee avatar, and labels.

Bug-Ticket Linking

Link bugs to helpdesk tickets when they describe the same problem. When the bug is fixed and closed, helpdesk agents are automatically notified so they can update customers.

Unique to Disqua: Bug report, customer ticket, and team channel discussion — all linked together. No other platform does this.

Email-in Setup

  1. 1Go to QA → Settings and add a QA mailbox (IMAP + SMTP credentials).
  2. 2Set the default project for incoming bugs.
  3. 3Disqua polls the mailbox every 2 minutes. New emails become bug reports automatically.
  4. 4Auto-reply confirms: "Bug #127 created: [subject]"

AI Auto-Triage

Every new bug is automatically analyzed by AI (Claude Haiku). The AI sets priority (from content analysis), classifies the type (bug, UI issue, performance, crash, security), and suggests relevant labels — all in under 2 seconds.