A bug report template is a fixed set of fields that makes everyone report a bug the same way. Pick the format below that matches where your bugs live, paste it in and delete anything you will not use.

Every template here covers the same core: where it happened, what you did, what you expected and what happened instead. For advice on writing each part well, read our guide to writing a bug report. This page is the copy-paste version.

Which template do you need?

Template	Use it when	Where it lives
Minimal	Quick internal reports on a small project	Chat, email, any tracker
Full	QA rounds and anything going to a development team	Word, Google Docs, any tracker
GitHub issue	Code is on GitHub and reporters have accounts	`.github/ISSUE_TEMPLATE`
Jira description	Your team runs Jira	The Description field
Spreadsheet	A one-off test round, or no tracker yet	Excel, Google Sheets
Client-friendly	Non-technical people are reporting problems	Email, shared doc, form

1. Minimal bug report template

Use this when speed matters more than detail. If someone cannot fill in these seven lines, the report is not ready to send.

Title:Page or screen (URL):What I did:What I expected:What happened instead:Browser and device:Screenshot or video:

2. Full software bug report template

This is the one to use for QA rounds and anything a developer will pick up cold. The triage block at the bottom is for the team, so reporters can leave it blank.

BUG REPORTID:Title: [Area] What goes wrong, and whenReported by:Date reported:ENVIRONMENTEnvironment: Production / Staging / DevelopmentURL or screen:Build or release:Browser and version:Operating system:Device and screen size:Logged in as (role only, never a password):DESCRIPTIONSummary (one or two sentences):Steps to reproduce:1.2.3.Expected result:Actual result:Happens: Every time / Sometimes / OnceWorked before: Yes / No / Not sureWorkaround:EVIDENCEScreenshot or video:Console or server errors:Test data used (never real customer data):TRIAGE (completed by the team)Severity: Critical / Major / Minor / TrivialPriority: Urgent / High / Normal / LowAssigned to:Status:Fixed in release:Retested by and date:

Using it in Word. Paste it into a blank document and bold the capitalised section headings. Then choose File, Save As and pick Word Template (.dotx) as the file type, so each new report opens as a fresh copy. For a form layout, select the lines that contain a colon, choose Insert, Table, Convert Text to Table, and separate at Other with a colon as the character. In Google Docs, keep one master and use File, Make a copy.

3. GitHub issue template in Markdown

Save this as .github/ISSUE_TEMPLATE/bug_report.md on your default branch. GitHub needs valid name and about keys in the front matter before it will show the template in the chooser.

---name: Bug reportabout: Report something that is brokentitle: "[Bug]: "labels: bugassignees: ''---## What went wrongOne or two sentences.## Steps to reproduce1.2.3.## Expected result## Actual result## Environment- URL:- Browser and version:- OS and device:- Environment: production / staging / local- Commit or release:## EvidenceDrag in a screenshot. Paste console or server errors in a code block.## Impact- [ ] Blocks a release or a key user journey- [ ] Has a workaround- [ ] Cosmetic only

4. Jira bug report template

Jira already gives you a Bug work type with fields for summary, priority, assignee and attachments. Do not repeat those. This text goes in the Description field only.

Steps to reproduce1.2.3.Expected resultActual resultEnvironmentURL:Browser and version:OS and device:Production or staging:Happens: Every time / Sometimes / OnceWorkaround:Console or server errors:

Making it appear automatically depends on your project type. Atlassian says you can set a default description in team-managed projects. In company-managed projects, the same article says default values on the system Description field are not supported. Its workaround is a paragraph custom field on the Create screen, plus a workflow post function that copies the value across. If that is more admin than you want, keep this text in a shared note and paste it in.

Save countless hours on your projects

Raise tasks in under 3 seconds using our revolutionary widget

5. Excel bug report template (spreadsheet columns)

Copy the block below and paste it into cell A1 of an empty sheet. The columns are separated by tabs, so each value lands in its own cell in Excel or Google Sheets. Row two is a fictional sample to overwrite.

ID	Title	Page URL	Steps to reproduce	Expected	Actual	Browser and device	Severity	Priority	Status	Owner	Reported by	Date raised	Date fixed	Screenshot link	NotesBUG-001	[Checkout] Place order does nothing with a discount code	https://staging.example-coffee.test/checkout	Add item, apply code TEST10, tap Place order	Order is placed	Spinner shows, no order created	iPhone 15, iOS 18, Safari 18	Critical	Urgent	New	Sam	Alex	2026-11-09 Fictional example

Three quick changes make it usable:

Add dropdowns. Select the Severity column, choose Data, Data Validation, List, and enter Critical,Major,Minor,Trivial. Do the same for Priority with Urgent,High,Normal,Low and Status with New,In progress,Fixed,Verified,Closed,Rejected.
Freeze the top row and turn on filters, so the team can view open bugs by owner.
Never delete a row. Close it instead, and never reuse an ID.

A spreadsheet is fine for one test round. It starts to struggle once you need notifications, screenshots in context or a history of who changed what.

6. Client-friendly bug report template

Clients and non-technical testers do not know their browser version and should not have to guess a severity level. These questions are written for them. The last question replaces severity, and the team translates it at triage.

Which page were you on?(Copy the web address from the top of your browser.)What were you trying to do?What did you expect to happen?What happened instead?Did it happen more than once?Yes / No / Not sureWhat were you using?(For example: iPhone with Safari, or a Windows laptop with Chrome.)How much is this getting in your way?I can't do what I need to / It's annoying but I can carry on / It just looks wrongPlease attach a screenshot if you can.

A filled-in bug report example

Here is the full template completed for a fictional bug on a fictional shop, Example Coffee Co. None of this comes from a real project.

ID: BUG-042Title: [Checkout] Place order button does nothing on iPhone after applying a discount codeReported by: Alex (QA)Date reported: 9 November 2026ENVIRONMENTEnvironment: StagingURL or screen: https://staging.example-coffee.test/checkoutBuild or release: 2026.11.2Browser and version: Safari 18Operating system: iOS 18Device and screen size: iPhone 15, 393 x 852Logged in as: Customer roleDESCRIPTIONSummary: After a discount code is applied, Place order stops responding on iPhone Safari, so the order cannot be completed.Steps to reproduce:1. Open /shop and add any coffee to the basket.2. Go to /checkout and fill in the delivery details.3. Enter discount code TEST10 and tap Apply. The total updates.4. Tap Place order.Expected result: The order is placed and the confirmation page loads.Actual result: The button shows a spinner for a moment and returns to normal. No order is created and no error appears on screen.Happens: Every timeWorked before: Yes, in release 2026.11.1Workaround: Remove the discount code and the order goes through.EVIDENCEScreenshot or video: bug-042-checkout.mp4Console or server errors: TypeError: Cannot read properties of null (reading 'value') at checkout.js:212Test data used: Test customer account on the sandbox payment gatewayTRIAGE (completed by the team)Severity: CriticalPriority: UrgentAssigned to: SamStatus: In progressFixed in release:Retested by and date:

Notice what makes it work. The title names the area, the trigger and the result. The steps start from a known page. The last good release narrows the search, and the workaround tells the team whether this has to be fixed tonight.

Who fills in which field

Templates fall over when nobody knows whose job a field is. This split works on most web projects:

Field	Completed by	Common mistake
Title, URL, steps, expected, actual	Reporter	A title such as "Checkout broken"
Browser, OS, device	Reporter or captured automatically	"Chrome" with no version
Screenshot, video, logs	Reporter or captured automatically	A cropped image with no URL visible
Severity	Reporter suggests, tester or developer confirms	Everything marked Critical
Priority, owner	Project lead or client lead	Set by whoever shouted last
Status, release, retest	Developer and tester	Closed without anyone retesting

Our severity and priority guide has a ready-made scale for those two fields, and the software bug life cycle covers what each status should mean.

Mistakes that make a template fail

Too many required fields. People skip reports or type "n/a" everywhere. Require the core and let the rest be optional.
Several bugs in one report. One report covers one bug, or half of it gets lost when the other half is closed.
Steps with gaps. If a stranger cannot follow them from a clean browser, they are not finished. See how to reproduce a bug.
Sensitive data in the report. Never paste passwords, card numbers or real customer details. Say which role or test account you used.
A template nobody reviews. After each project, delete any field that nobody filled in.

When typing it all out is the problem

The weak spot in any template is the technical detail someone has to type by hand. A visual bug reporting tool removes most of that typing. With QualityHive, someone clicks the element, types what is wrong and a task is created with a screenshot and the exact element pinned. Browser, OS and screen size are added on the Lite plan and above, and JavaScript errors on Mega and above.

Revolutionise your QA processes

FAQ

What should a bug report template include?

At minimum: a title, the page or screen, steps to reproduce, the expected result, the actual result, browser and device, and a screenshot or video. Add severity, priority and status once more than one person is working through the list.

Is there a bug report template for Word or Excel?

Yes. Paste the full template above into Word and save it as a .dotx template. For Excel, paste the tab-separated block into cell A1 and the columns are ready to use.

How do I add a bug report template to Jira?

Paste the Jira template above into the Description field. Team-managed projects can set it as a default description. Company-managed projects need the custom field workaround Atlassian documents, or a shared note to copy from.

Should clients use the same template as developers?

No. Give clients the plain-language version and let the team fill in severity, environment and steps once the report has been read. Asking clients for browser versions tends to produce guesses.

How many fields should a bug report have?

As few as your team actually uses. Seven lines is enough for a small project. Keep the longer version for formal QA rounds, where the triage and retest fields earn their place.