Use case
User acceptance testing without the shared spreadsheet
UAT is easy when stakeholders can send structured issues from the exact screen they’re looking at. Bugpot puts the widget on staging, gives each tester a form shaped like the test plan, and gives you an audit log you can hand back with sign-off.
The scenario
A client works through the pre-launch checklist
Instead of a Google Doc of “issue 14 — see screenshot in email”, every finding lands as a real issue with a screenshot, the exact URL and the environment they were on.
- 1
The client opens staging, works through the pre-launch checklist.
- 2
On any page they hit the feedback launcher — the form matches the test plan.
- 3
They mark up the screenshot, pick severity, submit; the screenshot and environment ship.
- 4
You triage each issue by status and priority, chase the last few, mark them resolved.
- 5
When testing wraps, you export the audit log to CSV as the paper trail for sign-off.
How Bugpot fits
The parts that carry this scenario
Widget on staging or preview
Set up staging as its own project so UAT feedback stays separated from production issues.
Forms shaped like the test plan
Add severity, area, browser and free-text repro. Different forms per issue type if the plan has separate checks.
Sign-off with an audit trail
Every status change, comment and assignment recorded with actor and timestamp — exportable as CSV.
Client-friendly language
Set the launcher label to “Report an issue”, choose the workspace branding — nothing on the widget shouts “developer tool”.
Relevant features
Where in the product you’ll live
Custom forms
Text, textarea, select, checkbox — required, optional and pre-filled defaults per issue type.
Read the deep dive →Custom issue types
Bug, blocker, cosmetic, question — each with their own colour, icon and form fields.
Read the deep dive →Session context
Browser, OS, viewport, URL, console log — attached to every UAT ticket automatically.
Read the deep dive →Audit log
Filterable audit trail with CSV export for the sign-off pack.
Read the deep dive →Comments & @mentions
Discussion lives on the issue so the reproduction back-and-forth stays with the ticket.
Read the deep dive →Integrations
Push confirmed UAT bugs into Jira, Linear or Azure DevOps once they’re accepted.
Read the deep dive →Run UAT with the paper trail intact
Spin up a staging project, put the widget on preview, and hand your stakeholders a real feedback tool.