Triage workflow
Feedback becomes a queue you can actually clear
Every report lands as an issue with a status, a priority and an owner. Comment, assign, filter, resolve — then watch it in analytics and pipe it out through webhooks. Built the way developers work through code review, not the way inboxes drown teams.
The inbox
Statuses, priorities, assignees — the essentials, done right
Every feedback item picks up a status the moment it arrives, and you move it through the same lifecycle every issue tracker uses.
- Priority: low, medium, high, critical — filterable in one click
- Assign to any team member; watch the queue by owner
- Filters for project, type, status, priority, assignee and reporter
- Bulk actions — resolve, reassign or change status across a selection
- Keyboard shortcuts everywhere, ⌘K palette to jump anywhere
- Pay button clipped below 400pxHighJWOpen
- Hero image blurry on retinaMediumASIn progress
- Cookie banner overlaps navMediumJWOpen
- Broken link in footerLow—Open
- Typo in shipping policyLowASResolved
Comments
Discussion on the issue, not in email
Comments live on the feedback item, threaded and time-stamped. Markdown for code snippets, links and lists. The full history stays with the issue when it’s resolved and archived.
- Markdown formatting with a live preview
- Fenced code blocks with syntax awareness
- @mention team members and get notified
- Editable, with a full edit history retained
Jamie2 hours ago
Reproduced on Safari iOS. The button’s width uses vw and clips on narrow viewports.
Alex14 minutes ago
Switching to min-width and a percentage — fix in review now.
Issue types
Custom types with colours, icons and their own forms
Not every report is a bug. Add issue types for suggestions, questions, praise or anything else you want reporters to be able to send — each with its own colour, icon and form fields.
Bug
Own colour, icon and form
Suggestion
Own colour, icon and form
Question
Own colour, icon and form
Praise
Own colour, icon and form
Webhooks
Signed deliveries into whatever you already use
Point Bugpot at Linear, Jira, Slack, Discord, Zapier or your own endpoint. Every event ships a JSON payload with an HMAC signature, and the full delivery log lives in the dashboard so you can inspect and replay.
- HMAC-SHA256 signed request bodies for verification
- Retries with exponential back-off on 5xx responses
- Delivery log with request, response and status per attempt
- Replay any past delivery from the dashboard
POST /hooks/bugpot
X-FF-Signature: t=1719939600,v1=b13a…
Content-Type: application/json
{
"event": "feedback.created",
"project": "clientsite",
"issue": {
"id": "fb_9k2p",
"type": "bug",
"title": "Pay button clipped …",
"priority": "high",
"reporter": { "name": "Sarah" }
}
}Audit log
Who changed what, when
Every status change, assignment, comment edit and setting update lands in the audit log with the actor, timestamp and previous value. Export the full log to CSV whenever your client, your compliance team or your future self needs it.
- Actor, action, target, before and after — for every event
- Filter by project, actor, event type and date range
- CSV export of any filtered view
- Retained for the lifetime of the workspace
- Alexchanged status Open → In progress10:14
- Jamiecommented on fb_9k2p09:51
- Alexassigned fb_9k2p to Alex09:22
- Systemcreated fb_9k2p from widget09:18
Analytics
The numbers behind the queue
Track feedback volume by project and issue type, watch median resolution times trend, and see who’s working through their queue. Analytics live per project and across your whole workspace.
Volume
Feedback per project, per week
Bug 24 · Suggestion 9
Resolution time
Median hours from open to resolved
18h · down 3h
Team performance
Resolved-per-assignee over range
Alex 41 · Jamie 33
AI assistance
Optional AI, only when your workspace enables it
Turn on AI assistance to have the inbox suggest better issue titles, rewrite messy reporter notes into clear descriptions, and translate reports from any language back into English. Off by default; scoped to the workspace; feedback text sent for processing only, never for training.
- Suggest — a concise, searchable title from the report body
- Rewrite — turn a rambling note into clear reproduction steps
- Translate — read any language report in your own
- Off by default; one toggle per workspace
Original
“hi the pay thing looks weird on my phone can’t click it, sarah”
Suggested title
Pay button not clickable on iOS viewports under 400px
Rewritten description
On Safari iOS at 390 × 844, the pay button overflows its container and cannot receive tap events. Reproduces on the checkout step of the pricing page.
Clear the queue instead of watching it grow
Statuses, priorities, comments, webhooks and analytics — free on every plan.