Reporter
Sees only their own bugs.
- Pages
- Home, My bugs, Uploads, Known issues, Release notes, Reporting guide
- Can start
- New bug, Upload a file
My bugs
Bug reporting portal for software teams
A bug reporting portal is where users report bugs with screenshots and steps to reproduce, the engineering team triages each report by severity on a board, and every reporter can see whether their bug has been fixed.
Pattern: RequestsDescribe it to Pory
“Our users report bugs with screenshots. Engineering triages them by severity, and whoever reported a bug should be able to see if it's been fixed.”
Viewing as
In plain English
How Pory sets it up
Pory gives every reporter and engineering a sign-in of their own. Each reporter sees only their own bugs. It covers report → triage → fix status. Bugs, asked of you, release notes and engineering team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Bug reports arrive with screenshots and repro steps attached
Bug reports used to be "the invoice thing is broken again" in a support email, with the screenshot promised and never sent. In Pory the reporter describes what happened, uploads screenshots, picks a severity, lists the steps to reproduce and names their browser. Engineering can start on it without a week of clarifying emails.
Forms to submit a recordDone by: Reporter
Engineering sorts reports by severity on one board, blockers first
Bugs arrived through support, sales and the CEO's text messages, and the loudest one got fixed first. In Pory each report is a card showing its severity, in Reported, Confirmed, Fix in progress, Fixed or Can't reproduce, and engineers drag it along as they work. The sales tax blocker gets attention before the blurry logo does.
Board by statusDone by: Engineering
Reporters see whether their bug is confirmed, in progress or fixed
Once a bug went into the tracker, the person who found it never heard about it again, so they reported it again. In Pory each reporter sees their own bugs with a progress bar from Reported to Fixed, including a Can't reproduce answer when that's the outcome, and the release each fix ships in. Duplicate reports drop, and so does "is this fixed yet?"
Status tracker for the submitterDone by: Reporter
Who sees what in a bug reporting portal
Every person signs in to their own view. This is what each role in the demo gets.
Engineering
Sees every bug in the portal.
- Pages
- Home, Bugs, Uploads, Known issues, Release notes, Reporting guide
What’s in the bug reporting portal template
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Bugs
- What happened (text)
- Screenshots (file)
- Severity (choice: Blocker, Major, Minor, Cosmetic)
- Steps to reproduce (long text)
- Browser or device (text)
- Reporter (link)
- Found on (date)
- Engineer (link)
- Latest from engineering (text)
- Status (choice: Reported, Confirmed, Fix in progress, Fixed, Can't reproduce)
Asked of you
- What we need (text)
- Bug (link)
- Needed by (date)
- File (file)
- Reporter (link)
- Status (choice: Requested, Uploaded, Checked)
Release notes
- Release (text)
- Date (date)
- Status (choice: Scheduled, Released)
- What it fixes (long text)
Engineering team
- Name (text)
- Role (text)
The parts behind this portal
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Collect
1 partForms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decide
2 partsStatus tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Board by status
Cards in columns. Drag a record to move it along.
Control
3 partsWho sees which records
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
Passwordless sign-in
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colors, your logo. Members see you.
Frequently asked questions
A reporter signs in with a link sent to their email and lands on Home. They see Home, My bugs, Uploads, Known issues, Release notes and Reporting guide, and only the bugs that are theirs. From there they can use “New bug” and “Upload a file”.
You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.
More customer support portals
All customer support portalsSupport ticketing portalSubmit & triageWarranty claims portalSubmit → approve → replaceReturns & RMA portalRequest → authorize → refundFeature request board portalSubmit → triage → plannedBeta program portalSignups, feedback, releasesCustomer feedback & NPS portalCollect & actProduct reviews portalSubmit → moderate → publish
Build your bug reporting portal with Pory
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited users.