When to use a bug tracking template
Bugs arrive from everywhere: customers, clients, support, testers and developers themselves. Without a clear workflow, the same bug is reported three times, critical issues wait behind cosmetic ones and fixes are released without anyone telling the person who reported them. A bug tracking template gives every bug the same path from report to close.
Use it for a product’s ongoing bug backlog, a client support retainer or the stabilisation period after a release. It suits software agencies, product teams and support teams that work with developers.
How the template is structured
- Report. Capture a complete report, check for duplicates and confirm the bug can be reproduced. Most wasted debugging time starts with an incomplete report.
- Triage. Set severity and priority using agreed definitions and assign an owner.
- Fix. Find the root cause, fix it with a test and review the change.
- Verify. Test on staging, release the fix and confirm with the reporter.
- Learn. Close with a note, review trends monthly and plan preventive work where bugs cluster.
The Needs info label marks bugs waiting on the reporter, and Regression marks bugs in features that used to work.
How to use it in Worklenz
- Start from the built-in Bug Tracking template during setup, or create a project with these phases.
- Create one task per bug and use the phases or a kanban board to move bugs from reported to closed.
- Use severity labels to filter critical bugs to the top.
- Assign owners and due dates based on priority.
- Track time on fixes on the Pro plan and above, which is useful for support retainers.
Making bug work visible and billable
For agencies, bug fixing often falls under a support retainer or a warranty period, and the time spent is easy to lose track of. Time tracking shows how much effort goes into bugs for each client and whether a retainer covers it. On the Business plan, the client portal lets clients submit issues as requests, so reports arrive in one place with the details you need.
Example: a support retainer for a client app
An agency maintains a client’s web app under a monthly support retainer. The client reports bugs through the client portal. Each report becomes a task, and the agency’s support lead triages it within one working day: a checkout error is critical and fixed the same day as a hotfix, while a misaligned icon is low priority and scheduled for the next release.
Developers add a test for every fix, and QA verifies on staging before release. At the end of the month, the monthly review shows that half of the bugs came from one older module, and the agency proposes a small refactoring project to the client.
Severity levels to start with
If your team has no agreed definitions yet, these four levels are a practical starting point. Critical: the product is down, data is at risk or customers cannot pay or sign in; fix immediately. High: a key feature is broken for many users and there is no workaround; fix in the current release. Medium: a feature is broken but a workaround exists, or few users are affected; schedule it. Low: cosmetic issues and small annoyances; fix when convenient. Write your definitions in the project description so everyone triages the same way.
Who should be involved
A triage owner, often a lead developer or QA lead, reviews new bugs and sets priority. Developers fix and review. QA verifies fixes. Support or account managers communicate with reporters and clients. A product owner decides priorities when bugs compete with new features.
Common bug tracking mistakes
The first mistake is accepting vague reports, which wastes developer time. The second is mixing severity and priority, so loud bugs get fixed before important ones. The third is never looking at patterns, so the same area keeps breaking. This template addresses each of these with its own step.
Tips for better bug tracking
- Use a report template. Ask for steps, expected and actual results every time.
- Define severity levels in writing. Everyone should rate bugs the same way.
- Add a test with every fix. It prevents the same bug from returning.
- Tell the reporter. Closing the loop builds trust with clients and users.
Related: the software development template and the quality assurance testing template.





