Editable bug tracker
Bug tracking template with realistic sample states
Use a focused register to see what is new, critical, assigned, ready for QA, failed, reopened or verified—then move beyond one sheet when the handoffs and evidence need connected records.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Sign in to inspect this populated view, then install the App with sample data to test the connected records, decisions and dashboards.
What the starter tracker covers
A bug tracking template should make backlog state easy to scan without pretending a spreadsheet is a full lifecycle system. Start with the fields and sample states that help prioritization, then use connected records when one bug needs multiple fixes, verification runs or release decisions.
- Eight populated bug states instead of an empty grid
- Practical severity, priority, owner and release fields
- Connected upgrade path without replacing the starter workflow
Start with the useful columns
A compact register still needs clear decision fields
These columns answer what happened, how serious it is, who acts next and where it stands.
- 01
Bug ID and title
Stable identifier plus a concise observable failure.
- 02
Component and release
The product surface and affected build.
- 03
Severity and priority
Separate consequence from work sequence.
- 04
Owner and state
The accountable next person and lifecycle position.
- 05
Reproduction context
Environment, steps and expected-versus-actual result.
- 06
Triage note
Why the report was accepted, returned, merged or deferred.
Editable Excel workbook
Download a working bug register—not an empty column list
The English workbook includes ten fictional bugs, prepared rows for additional reports, controlled choices, due-date signals and formulas for age, follow-up health and the next action.
- Normal, duplicate, deferred, failed, reopened, verified and closed examples
- Editable component, environment, severity, priority, status and owner fields
- Formula-driven age, due health and next-action columns
- A compact summary above the filterable bug register
Sample data
Learn from a realistic queue, not placeholder rows
The App includes state combinations that expose how the process behaves under pressure.
Critical and in fix
Payment confirmation timeout with a workaround and immediate owner.
Ready for QA
Offline sync duplicate fixed in a named release candidate.
Failed verification
Export columns restored but still in the wrong order.
Needs information
Login failure returned for missing browser and reset path.
Duplicate and deferred
One report merged; one low-impact issue held with a reason.
Verified and reopened
A passed sort fix and a mobile layout regression that returned.
When the template becomes a system
Add connected records when one row starts hiding the work
The register remains the issue owner; connected forms add depth without creating a competing page.
| Pressure | Add | Why |
|---|---|---|
| Several candidate fixes | Fix Work records | Preserve owner, code reference and target build per attempt. |
| Repeated or cross-build testing | Verification Runs | Keep each test environment and outcome. |
| Release go/no-go reviews | Release Readiness | Aggregate blockers and accepted known risk. |
| Many products and teams | Component and Release records | Maintain ownership and valid selections centrally. |
Questions and boundaries
Bug tracking template questions
Choose the starter register for a lightweight queue, or use the connected App when fix work and verification need their own history.
Can I use this instead of an Excel bug tracker?
Yes. Download the English Excel tracker for a single filterable register with sample records and status formulas. Use the Jodoo App when fixes, verification runs, release decisions, permissions and history need connected records rather than more columns in one file.
What statuses should a starter tracker use?
New, needs information, triaged, in fix, ready for QA, failed verification, reopened, verified and closed are a practical starting set. Keep duplicate and deferred as explicit triage outcomes.
How many fields are too many?
Show reporters only what they can supply. Keep triage, fix and QA fields for their owners or move them into connected forms as the process grows.
Does the template include sample data?
Yes. The product preview includes critical, duplicate, deferred, ready-for-QA, failed, reopened and verified examples.
Start from a working queue
Use the sample tracker, then adapt it as the process matures
Business teams can change fields, views and routing without rebuilding the App from code.