Bug Report Template (Free Download)

A tool-neutral bug report template that works in Excel or maps straight into Jira, with a filled example.

FreeNo sign-upUsed in our classes

.xlsx · 8 KB · Works in Excel and Google Sheets, with Jira-ready fields

bug-report-template.xlsxSheet 1 · 10 columns

fxPay button stays disabled after a valid UPI ID

	A	B	C	D
1	Bug ID	Title	Severity	Status
2	BUG-214	Pay button stays disabled after a valid UPI ID	High	Open
3	BUG-215	Cart total ignores coupon on refresh	Medium	Retest
4	BUG-216	Profile photo upload fails above 2 MB	Low	Fixed
5	BUG-217	Search returns no results for Hindi text	High	New
6	BUG-218	OTP email arrives after it expires	Critical	Closed

What a bug report includes

Ten fields make a bug report a developer can act on. Here’s what goes in each, with an example.

Bug IDA unique ID for tracking.BUG-214

TitleThe problem in one line, specific and searchable.Pay button stays disabled after a valid UPI ID

SeverityHow badly it affects users.High

PriorityHow soon it must be fixed.P1

EnvironmentDevice, OS, browser and build number.Android 14 · Chrome · build 3.8.1

Steps to reproduceNumbered steps anyone can follow.1. Add item 2. Checkout 3. Enter UPI ID

Expected resultWhat should happen.Pay button becomes active

Actual resultWhat happens instead.Pay button stays disabled

AttachmentsScreenshots, a screen recording or logs.screen-recording.mp4

StatusWhere the bug is in its life cycle.Open

Bug report example: checkout and search

Five real-style bugs at different stages, from new to closed.

NewOpenRetestFixedClosed

bug-log-sprint-12.xlsxSheet 1 · 10 columns

fxNew

	A	B	C	D
1	Bug ID	Title	Severity	Status
2	BUG-214	Pay button stays disabled after a valid UPI ID	High	Open
3	BUG-215	Cart total ignores coupon on refresh	Medium	Retest
4	BUG-216	Profile photo upload fails above 2 MB	Low	Fixed
5	BUG-217	Search returns no results for Hindi text	High	New
6	BUG-218	OTP email arrives after it expires	Critical	Closed

How to write a bug report developers can fix

One bug, clear steps, proof attached.

One bug per reportSplit combined problems, so each bug can be fixed, retested and closed on its own.
Write steps anyone can repeatStart from a known state and number every action. If a developer can’t reproduce it, it won’t get fixed.
State expected vs actualSay what should happen and what happens instead, in plain words.
Add the environmentDevice, OS, browser and build number: bugs often appear in only one of them.
Attach proofA screenshot, a short screen recording or the console log saves a round of questions.

Severity vs priority

Severity is about impact. Priority is about urgency. They’re set separately.

Answers: how bad is it?

Severity

How badly the bug affects the system or users. Usually set by the tester.

Example: OTP email arrives after it expires: critical, users can’t sign in.

Answers: how soon must it be fixed?

Priority

The order the team fixes bugs in, based on business need. Usually set by the product owner or lead.

Example: A typo in the homepage headline: low severity, but high priority before a launch.

FAQs

A record of a defect: what happened, how to reproduce it, and what should have happened.

One bug per report, repeatable steps, expected vs actual, the environment and proof.

Yes. Jira is widely used to log and track bugs.

More free tools

Test case templateExcel · Google SheetsGet it free Test plan templateWord · Google DocsGet it free Software testing MCQInstant score + explanationsStart the quiz

Learn to write these with a trainer

See the Manual Testing course

Stay in the loop

Get new batch dates on WhatsApp. One message when a batch opens, nothing else.

By subscribing you agree to receive WhatsApp messages from Tester Academy. Read our Privacy policy.