Every bug report needs a home, an owner, and a date. A software bug tracker gives your team all three, so a reported issue becomes a scheduled fix instead of a message that gets buried.
This guide covers a standard bug report format, severity vs. priority, scheduling fixes alongside planned work, and setup in TeamGantt.
What is a bug report?
A bug report is the roadmap you give developers so they can find and fix a software issue, like broken functionality or a feature that doesn’t display properly.
You might submit a bug report through a formal ticketing system or project management tool. That way your team can take the report and track the issue all the way to resolution.
One bug report describes one issue. The bug tracker holds every report, so the team can see what’s open, who owns each fix, and when it’s due.
Good software issue reporting means a developer can start on the fix without sending a follow-up message.
What is a software bug tracker?
A software bug tracker turns individual bug reports into a managed queue of fixes with owners and dates. Some teams call it defect tracking or issue tracking. Whatever the name, it does three jobs:
Capture each issue as a bug report with enough detail to reproduce it.
Triage each report by setting severity, priority, and an owner.
Schedule each fix so it lands at a known point before the release.
A tracker that stops at status tells you what’s broken. A schedule-first tracker also shows whether a fix fits before the release date, and what slips if it doesn’t.
A spreadsheet like Google Sheets works when you have a handful of bugs and one person triaging them. It starts to strain when you see these signals:
Several people are fixing bugs at the same time
One fix can’t start until another one ships
Bugs compete with planned sprint work for the same developers
When those signals show up, bug fixes belong inside your software development plan alongside feature work.
How to organize bug reports in a bug tracker
Organize your tracker by status first, then by feature if one area keeps breaking. Both layers work whether you log bugs in a project management tool or a simple Google Sheet.
Status of issue
Start by organizing bug reports by issue status. That way, there’s no question about where each issue stands in the resolution process, and the team can see every bug through to its fix.
Most software development teams sort issues into these 4 status categories:
Open: Newly submitted or ongoing bugs that haven’t been addressed yet
In progress: Issues that are actively being worked on by the team
On hold: Bugs the team started investigating but can’t move forward on just yet, whether it’s because more info’s required or other work needs to get done before the issue can be fixed
Closed: Issues that have been fully resolved by the team
Agree up front on who can move a bug to Closed, such as QA after verifying the fix, so nothing closes before it’s confirmed.
Features
Got a feature that’s particularly buggy? If you know it’s going to take multiple fixes to work out the kinks, consider organizing bugs into feature subgroups within each status category. Grouping related bugs helps your team spot patterns and fix them together.
How to write a bug report
A good bug report gives software developers a clear picture of the problem so they can resolve the issue more quickly. These must-haves are the pillars of any standard bug report.
Brief description of the bug
The first thing you’ll want to do is give that bug a name. Keep it short and sweet, with just enough detail to tell your software engineering team what’s happening and what feature or functionality is affected.
Steps to reproduce the bug
It’s also important to explain how you uncovered the defect in the first place. Consider these questions:
Does the issue happen sporadically, or can you duplicate it?
If the bug is reproducible, what steps does it take to recreate it?
The more detail, the better. If you can reproduce an issue, it’s much easier to find the cause.
Expected result
Your mom may have told you to shake “coulda, woulda, shoulda” from your vocabulary. But this line of thinking shines in bug reporting. Write down what should have happened when you took the steps that set the bug into action.
Actual result with a screenshot or screen capture
Now that you’ve laid your expectations out clearly, it’s time to describe the reality in all its ugly, buggy detail. Remember, a picture’s worth a thousand words. Attach a screenshot or screen capture of the issue to help your team pinpoint a resolution faster.
Next-level details to enhance your software bug report
If you really want to throw your dev team a solid, give them some additional info to work with. These extras can help your software engineers get to the root of the problem faster and figure out where the fix fits into the rest of their priorities.
Environment details
This is just a fancy way of saying: Where does the bug live and hide? Here’s how to point the way so your developers can hunt the defect down more quickly.
Which browsers are affected?
Is the problem happening on certain devices?
What operating system (OS) were you or the customer using?
Issue scope
Knowing how many customers the bug impacts, and even what it’s potentially costing you, helps your software engineering team determine the severity of the issue. That way they can prioritize the fix appropriately.
Browser console errors
The browser console gives developers a behind-the-scenes look at the web app action Chrome’s DevTools Console documentation shows you how to open the Console and read logged errors. Once you get there, you can take a screenshot of any errors you see logged in your console and attach it to your bug report.
Bug ID, reporter, and assignee
Give each bug a unique ID, like BUG-142, so the team can reference it in comments and commit messages. Record who reported it and when, so the developer knows who to ask about the steps. Then name one assignee who owns the fix, because shared ownership makes it easy for a fix to stall.
Here’s a filled-in bug report for a sample bug, using these elements:
Field | Example |
Bug ID | BUG-142 |
Title | Save button does nothing on the project settings page in Safari |
Reporter / date | QA tester, Tuesday, March 10 |
Environment | Safari 17, macOS 14, desktop |
Steps to reproduce | (1) Open the project settings page in Safari. (2) Change the project name. (3) Click Save. |
Expected result | The new name saves, and a confirmation message appears. |
Actual result | Nothing happens on click. The old name returns after a page refresh. |
Console error | TypeError: undefined is not an object (evaluating 'form.dataset.projectId') |
Severity | High |
Priority | P1 |
Scope | All Safari users who edit project settings |
Attachments | Screen recording of the failed save and a screenshot of the console error |
Assignee | Front-end developer |
Status | Open |
Bug severity vs. priority
Severity is how badly a bug breaks the software. Priority is how soon the team will fix it. The two often line up, but the exceptions are where scheduling gets tricky.
Combination | Example | How to schedule it |
High severity, high priority | Checkout crashes for every user the week before a launch | Fix it now, ahead of planned work |
High severity, low priority | An admin export crashes, but one internal user runs it monthly and has a workaround | Give it dates in a later sprint |
Low severity, high priority | A typo in the checkout button text on launch day | Fix it before the release milestone |
Low severity, low priority | An icon sits a few pixels off on an internal settings page | Park it in the backlog |
The reporter or QA sets severity, because they’ve seen the impact firsthand. The PM or product owner sets priority, because they know what else is competing for the same developers and dates. Many teams use a short scale for each, such as Critical, High, Medium, and Low for severity and P1–P4 for priority.
Priority is a scheduling decision. It answers one question: Which fix moves ahead of planned work? That’s why it belongs on the timeline as well as in a field. The TeamGantt section below shows how to make it visible with color-coding.
The same trade-offs show up in any project prioritization call, so the methods you already use to rank features carry over to bugs.
How to triage and schedule bug fixes
Triage decides which bugs get fixed now, and scheduling decides when. Use this five-step workflow to move each bug from report to a dated fix:
Log every report as its own task in the template’s Open group. One task per bug keeps the report, owner, and dates together.
Triage at a set time, like sprint planning or a weekly slot. Confirm the repro, then set severity, priority, and an owner in one pass.
Give fixes you’ll do now start and end dates before the next release milestone. Link related fixes with dependencies, so you can see what a slip affects.
Check capacity before you commit. In TeamGantt, Workloads shows each person’s assigned work, so you can spot who has room for an urgent fix.
Park bugs you’ll fix later in the product backlog. They stay out of the active sprint and remain visible for the next triage.
A set triage time keeps new bugs from interrupting the team one message at a time. Teams working in continuous flow triage bugs as they arrive. Sprint teams batch them at planning, as the Kanban vs. Scrum comparison explains.
When a bug moves to On hold, add the reason in its Comments. Anyone checking the tracker can then see what the fix is waiting on without asking.
How to track bugs in TeamGantt
In TeamGantt, your bug tracker works across three views, so developers, QA, and PMs can each work the way they prefer:
Schedule fixes in Gantt view. Use task scheduling to give the fixes you'll do now start and end dates, drag tasks between status groups or into a new order, and add dependencies so it's clear which fixes come first.
Write the report on the task. Put the full bug report in the task's Notes, formatted with markdown if you like. Use Comments for screenshots and back-and-forth until the bug is fixed.
Color-code priority or status. Task colors show priority, status, or who owns each fix at a glance.
Log and sort in List view. It offers the same drag and drop as the Gantt chart, in a simpler list.
Track progress in Board view. Turn your issue log into a board with a column for each status. You can set a column so tasks move there automatically at a certain percent complete, like moving a bug to Closed when it hits 100%.
Bug report and tracking template
Our bug report and issue tracking template gives you a ready-made tracker organized by issue status, so you can start logging bugs right away.
Copy-paste bug report format
If your team logs bugs through a form, email, or task tracker, use this bug report format so every report has the same fields.
In TeamGantt, you can paste it into the Notes for each bug so the full report lives on the task you schedule.