To make a Notion bug report form, create a Bugs database with properties for the summary, steps to reproduce, expected and actual results, environment and attachments, then add a Form view and share the link. Each report lands as a new row, ready to triage. The questions matter more than the layout, because they decide whether a developer can reproduce the bug.
What a Notion bug report form should ask
A Notion bug report form should collect the same things a good bug tracker asks for: a clear summary, steps to reproduce, what happened versus what was expected, and where it happened. Mozilla’s bug writing guidelines are a solid model, because Bugzilla has handled bug reports from the public for years.
Mozilla calls steps to reproduce the most important part of any bug report. It also asks reporters to separate facts from speculation, which is why expected and actual results get separate questions.
The questions, mapped to Mozilla’s guidance:
| Question | Notion property | Why it’s there |
|---|---|---|
| Summary | Title | Quickly and uniquely identifies the report |
| Steps to reproduce | Text | The part developers need most |
| What did you expect? | Text | Separates the expectation from the observation |
| What actually happened? | Text | The observed fact, including error text |
| How often does it happen? | Select: Always, Sometimes, Once | Mozilla asks if it reproduces always, occasionally or not at all |
| Where? (app, browser, OS) | Select or Text | Environment details |
| Version | Text | Earliest version where it shows up |
| Attachments | Files & media | Screenshots, recordings, logs |
| Optional, for follow-up |
A summary should describe the problem, not a proposed fix. Say so in the helper text: “Checkout button does nothing on Safari” beats “Fix the checkout button”.
How to build the bug report form in Notion
You build the form as a view of the Bugs database. Open the database, click + next to your views and pick Form. The full walkthrough is in how to create a form in Notion.
Then:
- Add the questions from the table, each connected to its property.
- Mark Summary, Steps to reproduce, Expected and Actual as Required. Notion won’t accept a submission until those are filled.
- Leave team-only properties off the form (see the next section).
- Turn on the email copy of each submission so new bugs don’t sit unseen.
- Share the link.
Notion’s forms guide says forms only work in the original database. If Form is missing from the menu, you’re in a linked view.
Screenshots and attachments
Notion’s forms guide lists files & media as a question type, so connect an Attachments question to a Files & media property. Mozilla also suggests a stack trace for crashes and a reduced testcase for web page bugs. Ask for both in the helper text. The post on Notion form file uploads covers the details.
Properties only your team fills in
The Bugs database needs fields the reporter never sees. These are where triage happens.
| Property | Notion type | Use |
|---|---|---|
| Bug ID | ID | A unique number nobody can change |
| Reported | Created time | When it came in |
| State | Status | New, Confirmed, In progress, Fixed, Won’t fix |
| Severity | Select | Your call, not the reporter’s |
| Owner | Person | Who’s on it |
| Duplicate of | Relation (to Bugs) | Links repeats to the original |
Notion’s property reference says ID values are unique and can’t be changed manually, so a bug’s ID stays a stable name in Slack threads and commit messages.
Keep Severity off the form. Reporters rate almost everything as urgent, and a field your team owns tells you more.
Who should be able to submit bugs
Who can submit decides how you share the form. Notion’s forms page offers workspace-only sharing and public sharing.
Internal testers. Share with your workspace. Named responses record who submitted in a Respondent or Created by property, so you know whom to ask about a vague report.
Customers or beta users. Share with Anyone on the web with link. These responses are automatically anonymous, which is why the form has an optional Email question. Reporters don’t need a Notion account; this guide explains why.
You can also link multiple forms to a single database, per Notion’s forms guide, so a short public form and a detailed internal one can both feed Bugs.
Triage new bug reports in Notion
Triage is the job of turning raw reports into a sorted queue. Do it in a dedicated view so the form’s raw output never becomes your backlog by accident.
Set up a Triage table view filtered to State is New, sorted by Reported. Per Notion’s views guide, each view keeps its own filters, so this doesn’t affect your main board. For Severity, drag the select options into order so sorting puts the worst first.
For each new row:
- Try the steps. If they work, set State to Confirmed.
- If the report covers two problems, split it. Mozilla asks for a new report for each issue.
- If it’s a repeat, fill Duplicate of and close it.
- Set Severity and Owner.
On a paid plan, a Page added trigger in database automations can set a default Owner or post a Slack notification for each new bug. The free plan only gets the Slack notification.
Where a native Notion form falls short for bug reports
A native form handles internal bug intake well, but it has gaps for public reporting. The biggest is branching: asking browser questions only for web bugs needs conditional logic, which Notion limits to the Business and Enterprise plans.
A public Notion form also looks like Notion, and it can’t read the reporter’s browser, so people have to type it.
Or use a form builder that writes to the same database. In nDBForms, conditional logic works with any Notion plan on the Pro tier, so a “Where did it happen?” answer can reveal the right follow-up questions.
The limitation: nDBForms saves uploads to your own Google Drive, up to 10 MB per file, and writes the link into Notion. Long screen recordings won’t fit, so ask for a link to the video instead. For similar intake setups, see the Notion IT support ticket template and conditional logic in Notion forms.
FAQ
Can people attach screenshots to a Notion bug report form?
Yes. Notion’s forms guide lists files & media among the question types. Add an Attachments question connected to a Files & media property for screenshots, screen recordings or logs.
Can a Notion form show different questions for app bugs and website bugs?
Only on the Business and Enterprise plans, where Notion offers conditional logic. On other plans, keep one short form or link separate forms to the same Bugs database.
How do I assign new bug reports automatically?
On a paid plan, a database automation with a Page added trigger can set the Owner property or send a Slack notification. On the free plan, automations are limited to Slack notifications.
Do bug reporters need a Notion account?
No, if you share the form with Anyone on the web with link. Those responses are anonymous, so add an optional email question if you want to follow up.