Report, triage, fix and verify software bugs with severity and environment on every card.
A bug tracking template is a ready-made board that records each software defect as a card and moves it through reporting, triage, fixing, review and testing until it is closed, with its severity and environment visible on the card.
Sign in with your Edesy account, then click Use template in the preview to create the board, with its sample cards, in your workspace.
Ideal for
Columns
Reported → Triaged → In progress → In review → Testing → Closed
Sample cards
8
Custom fields
Severity, Environment
Request form
Creates cards in Reported
Updated
2026-11-19
The 6 columns of this board with its 8 sample cards, labels and fields, as they open in Edesy Boards. Copy the template to move cards and edit it.
Labels
Critical, Regression, UI, Backend, Won’t fix
Custom fields
Severity (Single select, on card), Environment (Single select, on card)
Request form: Report a bug · Bug Tracking
Tell us what you need; it lands on the “Reported” column of this board. Asks for Title, Description, Severity, Environment, Attachments; each submission becomes a card in Reported.
Card templates
Bug report
Reported is the intake column for every new bug. Triaged means someone has reproduced it or at least checked it, confirmed the severity and assigned an owner, so developers only pick up bugs that are understood.
The limit stops the team from opening more fixes than it can finish. When the column is full, it is time to push fixes through review and testing rather than start new ones.
Separating code review from testing shows whether fixes are waiting on reviewers or on QA. The sample cards show a pull request under review and a Safari fix being verified on staging.
Closed completes the card, so the insights view counts fixed bugs. Bugs you decide not to fix can also be closed with the Won't fix label, which keeps a record of the decision.
Severity from S1 - Critical to S4 - Trivial tells the team what to fix first, separate from the card's priority, which reflects business urgency. Environment shows whether a bug affects live customers in Production or only Staging or Development.
Labels route work to the right people, UI for front-end and Backend for server work, and flag regressions, which usually need a test so they do not come back.
The form asks for a title, description, severity, environment and attachments, so a report includes what is needed to reproduce it. The card template gives bugs filed by developers the same checklist and fields.
This bug tracking board follows a defect from the moment someone reports it to the moment it is verified and closed. It has six columns: Reported, Triaged, In progress, In review, Testing and Closed. In progress carries a work-in-progress limit of 6 and Closed is the done stage. Two single-select fields sit on every card: Severity, from S1 - Critical through S2 - Major and S3 - Minor to S4 - Trivial, and Environment, with Production, Staging and Development in the samples. Five labels mark the type of bug: Critical, Regression, UI, Backend and Won't fix. The sample cards are typical of a web product team: an unresponsive checkout button on Safari 17, payment webhook retries creating duplicate orders with a reproduce, find root cause, fix, add test and verify in staging checklist, stale search results, an avatar upload regression, a fix waiting in code review, a Safari fix being verified on staging and a closed tooltip overlap on small screens. A Report a bug form lets testers, support staff or customers file bugs straight into Reported, and a Bug report card template keeps hand-filed bugs consistent.
It suits small software teams, startups and agencies that need a bug tracker their developers, testers and support staff can all use without learning a heavy tool. QA teams in Indian IT service companies can run one board per client project, and product teams can share the report form with support so customer-reported bugs arrive with steps, severity and screenshots.
Click Use this template, sign in with your Edesy account, then click Use template in the preview to create the board with its sample bugs.
Check the Severity and Environment options against your own definitions and release setup, and delete the sample cards.
Share the Report a bug form with testers and support; each report lands in Reported with a description, severity, environment and screenshots or logs as attachments.
Triage Reported daily: confirm severity, add labels, set priority and assign a developer, then move the card to Triaged.
Move cards through In progress, In review and Testing as the fix is built, reviewed and verified, and close them only after testing passes.
Severity, the custom field, describes how badly the bug breaks the product, from S1 - Critical to S4 - Trivial. Priority, the card's own setting, is how soon the team will fix it. A minor bug on a key page can be high priority.
Yes. Share the Report a bug form link with testers, support staff or customers. Each submission creates a card in Reported, with screenshots or logs attached.
An automation can act when a card gets the Critical label: set its priority to urgent, assign the on-call developer, post a message to a Slack channel or notify people in the app inbox.
There is no built-in Git integration. Paste the pull request link into the card or a comment, or use the REST API or webhooks to connect the board to your own tooling.
Use the list view to sort and group cards, filter by the Severity field, or export the board to CSV for a detailed report. The insights view shows cards by stage, label and assignee, and overdue cards.
Yes, by adding a label or custom field for the product. If each product has its own developers, separate boards created from the same template are easier to manage.
Yes, through the board request form. Share its public link; each submission becomes a card in the chosen column, with the answers in the card fields. Viewers of a shared read-only board link can see the board without an account.
Yes. Board automations run when a card is created, moved, assigned, labelled, completed, due soon or overdue, when a form is submitted or on a schedule, and can move, assign, label or archive the card, add a checklist or comment, create another card, call a webhook or post to Slack.
Log defects with severity and environment, triage them, fix and retest until they are closed.
6 columns · 7 sample cardsIncident Timeline TemplateReconstruct an incident minute by minute, from detection to mitigation and resolution, for the post-incident review.
5 columns · 6 sample cardsIssue Tracking With Web Clipper TemplateClip issues straight from web pages with URL and screenshot, then triage, fix and verify them.
6 columns · 7 sample cardsProject Management Issue Log TemplateLog project issues with owner, impact and resolution so nothing blocking the plan goes unnoticed.
5 columns · 7 sample cardsUAT Testing TemplateRun user acceptance testing: business users execute test cases, log defects and sign off on fixes.
6 columns · 8 sample cardsWebsite Bug Report TemplateCollect website bug reports through a form, triage by severity and track fixes through testing to closed.
6 columns · 6 sample cards