My bugs
Bug reporting portal
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
What is a bug reporting portal?
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. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (reporter and engineering) that shows only what that role should see, and flat pricing with unlimited users.
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 tax-rate 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. Duplicate reports drop, and so does "is this fixed yet?"
Status tracker for the submitterDone by: Reporter
The parts every portal is built from
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Forms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Public pages
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
Self sign-up
People create their own account and land in the role you chose for them.
File attachments
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Approve / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status 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.
Checklists
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Notes & scores
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Reminders by date
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Tables
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
People directory
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Calendar
Records on a month or week view, by date.
Gallery & image grid
Records as cards or photos.
Record pop-up & linked records
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the rows a viewer is allowed to read.
Control
Role & row access
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
No-Password Doors
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colours, your logo. Members see you.
On purpose
Four things Pory won’t do
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Take payments
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Book time slots
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
Host the conversation
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Plan routes
Pory keeps the service record, not the map.
Frequently asked questions
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
Your bug reporting portal, live today.
Describe it in a sentence and send the invite. Unlimited users, flat price.