Worklenz
Sign in
EN

Software & IT template

Bug Tracking Template

A simple bug tracking workflow: capture clear reports, triage and prioritise, fix with review, verify and close, then learn from patterns.

Worklenz has a built-in Bug Tracking template you can pick during setup, then shape it to match this plan.

  • Free plan available
  • Open source (AGPL-3.0)
  • Cloud or self-hosted
Developer investigating a software bug

What's included in the Bug Tracking template

phases
5
tasks
15
labels
6
statuses
3
1. Report · 3 tasks
  • Capture the bug reportSteps to reproduce, expected and actual result, environment, screenshots and who reported it.
  • Check for duplicatesSearch existing bugs and merge duplicates so there is one record per problem.
  • Confirm the bug can be reproducedReproduce the problem, or ask the reporter for the missing details.
2. Triage · 3 tasks
  • Set severityRate impact, from cosmetic to critical, using agreed definitions.
  • Set priorityDecide when it will be fixed, based on severity, number of users affected and deadlines.
  • Assign an ownerGive the bug to the developer best placed to fix it.
3. Fix · 3 tasks
  • Find the root causeIdentify why the bug happens, not just where.
  • Implement the fixFix the problem and add a test that would have caught it.
  • Code reviewAnother developer reviews the fix before it is merged.
4. Verify · 3 tasks
  • Test the fix on stagingConfirm the bug is fixed and nothing nearby is broken.
  • Release the fixDeploy the fix in the next release, or as a hotfix for critical bugs.
  • Confirm with the reporterLet the reporter know it is fixed and ask them to confirm.
5. Learn · 3 tasks
  • Close the bugClose with a short note on the cause and the fix.
  • Review bug trends monthlyLook for areas of the product that produce repeated bugs.
  • Plan preventive workAdd tests, refactoring or documentation where bugs cluster.

Labels

  • Critical
  • High
  • Medium
  • Low
  • Needs info
  • Regression

Who this template is for

  • Software agencies handling bug reports from several clients
  • Product teams that need a lightweight bug workflow
  • Support teams passing customer issues to developers

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

  1. Report. Capture a complete report, check for duplicates and confirm the bug can be reproduced. Most wasted debugging time starts with an incomplete report.
  2. Triage. Set severity and priority using agreed definitions and assign an owner.
  3. Fix. Find the root cause, fix it with a test and review the change.
  4. Verify. Test on staging, release the fix and confirm with the reporter.
  5. 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

  1. Start from the built-in Bug Tracking template during setup, or create a project with these phases.
  2. Create one task per bug and use the phases or a kanban board to move bugs from reported to closed.
  3. Use severity labels to filter critical bugs to the top.
  4. Assign owners and due dates based on priority.
  5. 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.

Start your bug tracking project in Worklenz

Sign up free, then set up the phases and tasks above for your team.

Bug Tracking template FAQs

What should a good bug report include?

Steps to reproduce, expected result, actual result, the environment such as browser or device, screenshots or recordings, and who reported it.

What is the difference between severity and priority?

Severity describes how badly the bug affects users. Priority describes when the team will fix it. A severe bug in a rarely used feature may still have a lower priority than a moderate bug on a key page.

Is this bug tracking template free?

Yes. The full template is on this page, and Worklenz's free plan includes task lists, kanban boards and built-in project templates.

Does Worklenz have a built-in bug tracking template?

Yes. Worklenz includes a built-in Bug Tracking template you can pick during account setup and adapt to this workflow.

Software & IT

Software Development template

Plan and deliver a software project in sprints: requirements, technical design, iterative development, testing, release and early support.

6 phases · 18 tasks. By Worklenz.

Software & IT

E-commerce Development template

Build or rebuild an online store: discovery, platform and design, product catalogue, checkout, payments and shipping, testing and a launch that protects sales.

6 phases · 19 tasks. By Worklenz.

Software & IT

IT Project template

Plan an IT project such as a system rollout, upgrade or migration: assess needs, plan and procure, implement, roll out to users and hand over to support.

6 phases · 18 tasks. By Worklenz.

Software & IT

Data Migration template

Move data between systems safely: assess and map the data, clean it, run test migrations, cut over with a rollback plan and validate the results.

6 phases · 17 tasks. By Worklenz.

Software & IT

QA Testing template

Plan and run software QA: define scope and approach, write test cases, prepare environments, execute tests, track defects and sign off the release.

5 phases · 15 tasks. By Worklenz.

Software & IT

Security Assessment template

Run a security assessment from scope to remediation: inventory assets, review risks and controls, test for vulnerabilities, report findings and track fixes to closure.

6 phases · 17 tasks. By Worklenz.

Explore more templates

Run your next project from a template

Worklenz is an open-source platform for agencies and service teams: projects, time tracking and client work in one place.