Website Bug Report Template: Steps, Results, and Context
Write a useful website bug report with reproducible steps, actual and expected results, environment details, and frequency. Includes a concrete form example.
A useful website bug report separates the conditions, actions, observed result, and expected behavior. Record what you saw before deciding what caused it.
For a proposed wording or layout improvement, use the website change request template. This guide focuses on behavior that appears to fail an expectation.
Copy this report template
Subject: [Page or action] causes [observed problem]
URL: An address appropriate to share
Observed at:
Environment: Production/staging, OS, browser version, viewport width
Preconditions: Login state, role, selected options
Steps:
1.
2.
3.
Actual result:
Expected result:
Basis for the expectation: UI guidance, specification, or earlier observation
Frequency: Attempts and occurrences, or unconfirmed
User impact:
Images, recording, or visible error:
Unknowns and checks already performed:If you do not know the specification, say so. Keep your preference or assumption separate from an agreed requirement.
Make the steps executable by another person
“Submit the form” omits the selected options and entered data. Explain which page to open, what to enter, and which controls to use.
This example uses a fictional test environment:
Subject: Returning from contact confirmation clears the selected inquiry type
Precondition: Staging environment, signed out
Steps:
1. Open the contact page.
2. Select “Adoption inquiry” and fill required fields with test data.
3. Select “Review.”
4. Select “Back to editing” on the confirmation screen.
Actual result: Inquiry type is empty; other fields remain populated.
Expected result: The selected inquiry type remains available for editing.
Basis: The page says users can return to edit; detailed specification unconfirmed.
Frequency: Observed in all three attempts under these conditions.Replace the environment and counts with your own observations. Form submissions can create real messages or orders, so use an authorized test environment or procedure when reproducing them.
Keep observations separate from a suspected cause
“Saving is broken” provides less evidence than “Selecting Save shows an error, and the new item does not appear in the list.”
If you have a hypothesis, label it. Do not identify the network, browser, or implementation as the confirmed cause without checking it.
Record intermittent problems honestly
For an issue seen once, record the time, preceding actions, error display, and subsequent attempts. A failed reproduction is useful when you explain which conditions you did and did not match.
Mozilla's bug-writing guidance emphasizes reproducible steps, actual and expected results, and distinguishing observation from speculation. This template applies those principles to a website report.
Use a pin for location and a report for the sequence
Fusenly can mark the element with a pinned comment and hold the steps in a page note. Use these for your observations, then transfer the formal report to the agreed issue tracker or shared channel.
A pin does not preserve the sequence of interactions or the earlier screen state. Capture images or video separately where needed. Fusenly does not capture screenshots or recordings, or attach browser logs automatically.
Review before sharing and after a fix
Remove temporary credentials and unrelated personal data from URLs, screenshots, and logs. Use test data instead of real customer information. Check that environments and attempt counts described as verified were actually tested.
After a fix, repeat the recorded steps and report whether the expected behavior occurred. Include the scope you verified so another condition is not mistaken for the same result.
Source
Official guidance and Fusenly features checked on October 31, 2026.
Related articles
- Write Clear Website Change Requests: A Practical Template
Write website change requests with a URL, location, current behavior, expected result, and acceptance checks. Includes a template and concrete examples.
- How to Comment on a Website: Notes and Pinned Annotations
Add comments and annotations to web pages in Chrome. Follow the pin workflow and understand personal notes, team feedback, and public website comments.
- Take Better Notes on Technical Articles: Record Experiments and Questions
Turn technical articles and official documentation into useful study notes by recording your goal, environment, experiments, results, and next question. Includes a reusable template.