Checkout page returns 500 on card decline
Customers report a blank 500 error page instead of a decline message when a card is rejected at checkout. Reported via support ticket #4821.
Engineering
Bug Triage Board
Bug Triage Board: Sort Defects by Severity, Owner, and Fix Status
Engineering teams drowning in incoming bug reports need a fast, structured way to separate P0 fires from low-priority polish items. This Bug Triage Board template uses five clear columns - Incoming, Triaged, In Progress, Fixed - Awaiting Verify, and Closed - to move defects through a predictable pipeline from first report to verified fix. Built on Kanboard's kanban board with MCP server support, the board lets both humans and AI agents create, update, and move bug tasks programmatically, tagging severity (P0-P3) and owner directly in task descriptions. Because the free plan caps you at 1 project and 25 tasks, this template is designed to stay lean: verified fixes get pruned from Closed regularly so the board never becomes bloated. Teams handling higher bug volume or running multiple product lines can upgrade to Pro for $12/mo or $96/yr to unlock more projects. Whether you're a solo developer triaging your own reports or a team coordinating fixes across owners, this board gives you a concrete starting point you can adopt today.
kanboard.io/templates/bug-triage
Template preview
Bug Triage Board
5 columns
Incoming
2New defects reported by users, QA, or monitoring alerts land here before anyone reviews severity or owner.
Push notifications duplicated on Android 14
Users on Android 14 receive the same push notification 2-3 times within a minute. Logged from crash analytics dashboard.
Triaged
2Bugs that have been reviewed and tagged with severity (P0-P3) and an assigned owner, waiting to be picked up.
P1: Search autocomplete crashes on empty query
Severity P1, owner @maria. Search bar throws JS exception when user hits enter with no text entered.
P2: CSV export missing timezone offset
Severity P2, owner @jorge. Exported reports show UTC timestamps without offset, causing confusion for EU customers.
In Progress
2Owner is actively working on a fix; card stays here until a patch or PR is ready for verification.
Fixing race condition in payment webhook handler
Owner @sara actively debugging duplicate webhook processing causing double charges. PR branch fix/webhook-race open.
Patching memory leak in image upload service
Owner @devon tracing leak in thumbnail generation microservice, reproduced locally, working on fix.
Fixed - Awaiting Verify
2A fix has been merged or deployed and is waiting for QA or the reporter to confirm the defect is resolved.
Verify: login timeout on slow connections
Fix deployed to staging by @maria. Needs QA to confirm timeout no longer occurs on throttled 3G connection profile.
Verify: dark mode toggle not persisting on refresh
Fix deployed by @jorge. Waiting on original reporter to confirm the setting now persists after page reload.
Closed
2Bug confirmed fixed and verified; kept briefly for record-keeping, then pruned to stay under task limits.
Fixed: signup form allowed duplicate emails
Confirmed resolved by QA on build 2.14.3. Owner @sara. Ready for deletion after sprint review to free up task slots.
Fixed: broken pagination on admin user list
Verified fixed by reporter. Owner @devon. Archive or delete before next triage cycle to stay under the 25-task free limit.
How to run this board
Step 1
New defects are logged in the Incoming column as soon as they're reported by users, QA, or monitoring tools, with no severity assigned yet.
Step 2
A triager reviews each Incoming bug, tags it with severity (P0-P3) and an owner in the description, then moves it to Triaged using move_task.
Step 3
The assigned owner picks up the bug from Triaged and moves it to In Progress while actively working on a fix.
Step 4
Once a fix is deployed, the card moves to Fixed - Awaiting Verify until QA or the original reporter confirms the issue is resolved.
Step 5
Verified bugs move to Closed, and older Closed tasks are periodically deleted with delete_task to stay within the free plan's 25-task limit.
AI agent usage
Run it with AI agents
This Bug Triage Board gives engineering teams a lightweight, MCP-driven workflow for sorting incoming defects by severity, owner, and fix status. Agents connected via the MCP server can file new bugs, reclassify severity, reassign owners, and move cards through the pipeline automatically using the standard Kanboard MCP tools (create_task, update_task, move_task, list_tasks, get_task). Because the free plan caps usage at 1 project and 25 tasks, teams should treat this board as a live triage queue rather than a permanent archive: closed/fixed bugs should be pruned with delete_task or exported before hitting the limit. Pro upgrades ($12/mo or $96/yr) remove the task cap and allow multiple concurrent project boards, useful for teams tracking bugs across several products at once.
## Bug Triage Board (Kanboard MCP)
Columns: Incoming, Triaged, In Progress, Fixed - Awaiting Verify, Closed
Agents should use `list_tasks` to pull the current board state before creating new entries with `create_task`, always tagging severity (P0-P3) and owner in the task description since Kanboard's MCP tools do not have native severity/owner fields. Use `move_task` to shift cards left-to-right as status changes (Incoming -> Triaged -> In Progress -> Fixed - Awaiting Verify -> Closed). Use `update_task` to edit descriptions when owner or severity changes without moving columns. Before adding a task, check total task count against the free-plan limit of 25 tasks; if at capacity, `delete_task` on Closed items older than the current sprint. Never invent column names or fields outside: Incoming, Triaged, In Progress, Fixed - Awaiting Verify, Closed.Move the login-timeout bug from Triaged to In Progress and assign it to @sara
List all P0 tasks currently sitting in the Incoming column
Create a new bug task for the checkout page 500 error and put it in Triaged with owner @devon
Learn more about the board-centric workflow in Kanban for AI Agents or open the MCP guide.
Frequently asked questions
How does this board handle severity and owner if Kanboard doesn't have dedicated fields?
Severity (P0-P3) and owner are tagged directly in the task title or description, since the MCP tools (create_task, update_task) only expose title and description fields. Sorting by severity and owner is done via naming convention and manual scan or list_tasks filtering.
What happens when I hit the 25-task limit on the free plan?
You'll need to delete completed tasks from the Closed column using delete_task before adding new bugs. The free plan is capped at 1 project and 25 tasks total across all columns, so active triage boards should be pruned regularly.
Can I run separate bug boards for multiple products on the free plan?
No, the free plan only supports 1 project. To run multiple bug triage boards simultaneously for different products, you'd need the Pro plan at $12/mo or $96/yr, which allows more than one project.
Can an AI agent move bugs through the pipeline automatically?
Yes, agents connected via the MCP server can use move_task to shift cards between Incoming, Triaged, In Progress, Fixed - Awaiting Verify, and Closed, and use update_task to edit severity or owner details in the description.
Does this board integrate with our existing bug tracker?
This template runs on Kanboard's own kanban board using the REST API or MCP server for programmatic access. It does not include integrations beyond what Kanboard natively supports; you would need to manually or programmatically sync data if using an external tracker.
Is there a keyboard-driven way to triage bugs quickly?
Yes, Kanboard supports keyboard shortcuts and a command palette in the app for fast navigation between tasks and columns, in addition to the macOS app for desktop use.
Related templates
Ready to create this board?
Sign in and use the template to create a project with columns and sample tasks.