[{"data":1,"prerenderedAt":935},["ShallowReactive",2],{"blog-posts":3,"post-\u002Fblog\u002Fbug-triage-process":351},[4,19,29,39,50,61,72,84,103,117,131,146,157,169,183,195,205,216,229,238,252,261,273,285,296,307,318,330,339],{"path":5,"title":6,"description":7,"date":8,"modified":8,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":13,"readingTime":18},"\u002Fblog\u002Fbug-triage-process","Bug Triage Process: Steps, Meeting Agenda and Free Checklist","A bug triage process for web teams: the steps, who attends the bug triage meeting, a 30-minute agenda, a triage matrix and a free Word checklist.","2026-11-18T08:00:00+00:00",false,"en","guides",null,[14,15,16,17],"bug triage process","bug triage meeting","bug triage matrix","defect triage",9,{"path":20,"title":21,"description":22,"date":23,"modified":23,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":24,"readingTime":18},"\u002Fblog\u002Fwebsite-change-request-form","Website Change Request Form: Free Template, Change Log and Process","A free website change request form (Word) and change log (Excel), how to tell a change from a bug, and a process to quote, approve and ship updates.","2026-11-12T08:00:00+00:00",[25,26,27,28],"website change request form","website update request form","website change request template","change request template",{"path":30,"title":31,"description":32,"date":33,"modified":33,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":34,"readingTime":18},"\u002Fblog\u002Fjira-bug-report-template","Jira Bug Report Template: Free CSV Import and Field Guide","A Jira bug report template you can import: a free CSV with four example bugs, a field guide, a description to paste and how to write a bug report in Jira.","2026-11-10T08:00:00+00:00",[35,36,37,38],"jira bug report template","how to write a bug report in jira","jira defect report template","jira bug tracking template",{"path":40,"title":41,"description":42,"date":43,"modified":43,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":44,"readingTime":49},"\u002Fblog\u002Fwebsite-feedback-form-questions","Website Feedback Form Questions: 45 Examples by Goal (Free Template)","Website feedback form questions for visitors, customers and clients: 45 examples grouped by goal, three ready-made forms and a free Excel question bank.","2026-11-05T08:00:00+00:00",[45,46,47,48],"website feedback form questions","website feedback form template","website feedback form examples","website feedback survey questions",11,{"path":51,"title":52,"description":53,"date":54,"modified":54,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":55,"readingTime":60},"\u002Fblog\u002Fbug-severity-vs-priority","Bug Severity vs Priority: Differences, Examples and a Free Matrix","Bug severity vs priority: what each one measures, severity levels, website examples where they disagree and a free Excel matrix that suggests priority.","2026-11-03T08:00:00+00:00",[56,57,58,59],"bug severity vs priority","bug severity levels","bug severity matrix","severity and priority examples",10,{"path":62,"title":63,"description":64,"date":65,"modified":65,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":66,"readingTime":71},"\u002Fblog\u002Fwebsite-handover-checklist","Website Handover Checklist: 43 Items to Hand Over at Launch (Free Template)","A website handover checklist for agencies and freelancers: accounts, domain, hosting, backups, licenses and support terms, plus a free handover document.","2026-10-29T08:00:00+00:00",[67,68,69,70],"website handover checklist","website handover document template","website handover process","web agency",12,{"path":73,"title":74,"description":75,"date":76,"modified":76,"draft":9,"locale":10,"category":77,"image":12,"translationKey":12,"tags":78,"readingTime":83},"\u002Fblog\u002Fclaude-code-fix-bugs","How to Use Claude Code to Fix the Bugs Your Clients Report","How to use Claude Code to fix bugs: what it needs from a bug report, how to connect it to client feedback over MCP, and how to review the fix before you resolve it.","2026-10-27T08:00:00+00:00","workflow",[79,80,81,82],"claude code fix bugs","claude code mcp","ai bug fixing","bug report",7,{"path":85,"title":86,"description":87,"date":88,"modified":89,"draft":9,"locale":10,"category":11,"image":90,"translationKey":96,"tags":97,"readingTime":102},"\u002Fblog\u002Fbest-website-feedback-tools","How to Choose a Website Feedback Tool (2026 Checklist)","How to choose the best website feedback tool in 2026: the tool types, 12 criteria, a free scoring template (Excel) and a one-week trial plan with a real client.","2026-10-07T09:00:00+00:00","2026-10-22T10:00:00+00:00",{"src":91,"card":92,"alt":93,"width":94,"height":95},"\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback-400x250.jpg","Code on a screen, illustrating how to choose a website feedback tool",1200,630,"feedback-tools",[98,99,100,101],"best website feedback tool","website feedback tool free","visual website feedback tool","client feedback",8,{"path":104,"title":105,"description":106,"date":88,"modified":89,"draft":9,"locale":10,"category":77,"image":107,"translationKey":112,"tags":113,"readingTime":102},"\u002Fblog\u002Fclient-website-approval","Client Website Approval: How to Get Sign-Off Without Delays","Client website approval made simple: the 5 approval stages, a revision-limit clause, a sign-off email, a free website sign-off form (Word) and a checklist.",{"src":108,"card":109,"alt":110,"width":111,"height":94},"\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized-400x250.jpg","Two people reviewing a printed document with a pen, ready for client website approval",1920,"client-approval",[114,115,116,70],"client approval process","website sign off","revision rounds",{"path":118,"title":119,"description":120,"date":88,"modified":89,"draft":9,"locale":10,"category":11,"image":121,"translationKey":125,"tags":126,"readingTime":18},"\u002Fblog\u002Fhow-to-collect-client-feedback-on-a-website","How to Collect Client Feedback on a Website (Step by Step)","How to collect client feedback on a website: 5 methods compared, a review round step by step, good vs vague feedback examples and a briefing email to send today.",{"src":122,"card":123,"alt":124,"width":94,"height":95},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback-400x250.jpg","Web designer at a desk reviewing client feedback on a website","client-feedback",[127,128,129,130],"client feedback on website","website feedback examples","client feedback examples","website review process",{"path":132,"title":133,"description":134,"date":88,"modified":89,"draft":9,"locale":135,"category":11,"image":136,"translationKey":140,"tags":141,"readingTime":83},"\u002Fes\u002Fblog\u002Fanotar-capturas-de-pantalla-web","Cómo anotar capturas de pantalla de una web (Mac, Windows y online)","Cómo anotar capturas de pantalla en Windows, Mac, online o en Chrome, cómo capturar una página web entera y cómo marcar los errores para que se arreglen.","es",{"src":137,"card":138,"alt":139,"width":94,"height":95},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback-400x250.jpg","Persona anotando capturas de pantalla de una web para enviarlas al equipo de desarrollo","screenshot-annotation",[142,143,144,145],"anotar capturas de pantalla","captura de pantalla","anotar captura en Mac","anotar captura en Windows",{"path":147,"title":148,"description":149,"date":88,"modified":89,"draft":9,"locale":135,"category":77,"image":150,"translationKey":112,"tags":152,"readingTime":102},"\u002Fes\u002Fblog\u002Faprobacion-cliente-proyecto-web","Aprobación del cliente en un proyecto web: cómo conseguirla","Aprobación del cliente en un proyecto web: las 5 fases, una cláusula para limitar revisiones, un email de aprobación, un formulario de aprobación gratis y una checklist.",{"src":108,"card":109,"alt":151,"width":111,"height":94},"Dos personas revisan un documento con un bolígrafo antes de la aprobación del cliente en un proyecto web",[153,154,155,156],"aprobación del cliente","rondas de revisión","presupuesto web","agencia web",{"path":158,"title":159,"description":160,"date":88,"modified":89,"draft":9,"locale":135,"category":77,"image":161,"translationKey":163,"tags":164,"readingTime":18},"\u002Fes\u002Fblog\u002Fcapturas-anotadas-en-asana","Capturas anotadas en Asana: cómo llevar el feedback web a tareas","Cómo llevar capturas anotadas y feedback web a Asana: plantilla CSV gratis, cinco métodos comparados y tareas automáticas desde el feedback del cliente.",{"src":91,"card":92,"alt":162,"width":94,"height":95},"Capturas anotadas de una web convertidas en tareas de Asana","asana",[165,166,167,168],"capturas anotadas en Asana","plantilla Asana","gestión de bugs","feedback web",{"path":170,"title":171,"description":172,"date":88,"modified":89,"draft":9,"locale":135,"category":11,"image":173,"translationKey":177,"tags":178,"readingTime":71},"\u002Fes\u002Fblog\u002Fchecklist-qa-web-antes-de-lanzar","Checklist web: más de 70 comprobaciones antes de lanzar","Checklist web con más de 70 comprobaciones por áreas: formularios, enlaces, móvil, navegadores, velocidad, SEO, accesibilidad y WordPress, con plantilla Excel gratis.",{"src":174,"card":175,"alt":176,"width":94,"height":95},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback-400x250.jpg","Persona revisando una web con una checklist QA antes del lanzamiento","qa-checklist",[179,180,181,182],"checklist web","checklist QA web","pruebas web","lanzamiento web",{"path":184,"title":185,"description":186,"date":88,"modified":89,"draft":9,"locale":135,"category":11,"image":187,"translationKey":189,"tags":190,"readingTime":18},"\u002Fes\u002Fblog\u002Fcomo-escribir-un-informe-de-bugs","Plantilla de reporte de errores (bugs): gratis, con ejemplos","Plantilla de reporte de errores gratis en Excel, Google Sheets y Word, con un ejemplo de informe de bugs bueno y uno malo y los campos que importan en una web.",{"src":91,"card":92,"alt":188,"width":94,"height":95},"Código JavaScript en una pantalla, ilustrando cómo escribir un informe de bugs de una web","bug-report",[191,192,193,194],"plantilla de reporte de errores","reporte de errores","informe de bugs","ejemplo de reporte de errores",{"path":196,"title":197,"description":198,"date":88,"modified":89,"draft":9,"locale":135,"category":11,"image":199,"translationKey":125,"tags":201,"readingTime":18},"\u002Fes\u002Fblog\u002Fcomo-recoger-feedback-de-clientes-en-una-web","Cómo pedir feedback a un cliente sobre su web (paso a paso)","Cómo pedir feedback a un cliente sobre su web: 5 métodos comparados, una ronda de revisión paso a paso, ejemplos de feedback bueno y vago y un email para enviar hoy.",{"src":122,"card":123,"alt":200,"width":94,"height":95},"Diseñador web en su mesa revisando el feedback de clientes sobre una web",[202,203,168,204],"cómo pedir feedback a un cliente","feedback de clientes","revisión de una web",{"path":206,"title":207,"description":208,"date":88,"modified":89,"draft":9,"locale":135,"category":77,"image":209,"translationKey":211,"tags":212,"readingTime":102},"\u002Fes\u002Fblog\u002Ffeedback-web-en-notion","Bugs en Notion: gestiona el feedback de tu web paso a paso","Cómo gestionar bugs en Notion en proyectos web: plantilla gratis, propiedades, vistas tablero, rutina de triaje y cómo recibir el feedback del cliente solo.",{"src":108,"card":109,"alt":210,"width":111,"height":94},"Equipo organizando bugs y feedback de clientes de una web en Notion","notion",[213,214,215,168],"bugs en Notion","plantilla Notion","seguimiento de bugs",{"path":217,"title":218,"description":219,"date":88,"modified":89,"draft":9,"locale":135,"category":220,"image":221,"translationKey":223,"tags":224,"readingTime":18},"\u002Fes\u002Fblog\u002Fherramientas-gratis-seguimiento-bugs","Herramientas gratis de seguimiento de bugs para webs (2026)","Herramientas gratis de seguimiento de bugs para equipos web: los planes gratuitos de Jira, Trello, ClickUp, Notion, Asana, monday.com y Wrike, y una hoja de cálculo gratis.","comparisons",{"src":174,"card":175,"alt":222,"width":94,"height":95},"Equipo revisando incidencias en una herramienta gratis de seguimiento de bugs","free-bug-tracking",[225,226,227,228],"herramientas gratis seguimiento de bugs","bug tracker","gestión de incidencias","hoja de seguimiento de bugs",{"path":230,"title":231,"description":232,"date":88,"modified":89,"draft":9,"locale":135,"category":11,"image":233,"translationKey":96,"tags":235,"readingTime":18},"\u002Fes\u002Fblog\u002Fmejores-herramientas-feedback-visual-web","Cómo elegir una herramienta de feedback visual para tu web","Cómo elegir entre las herramientas de feedback visual web en 2026: tipos, 12 criterios, una plantilla de evaluación gratis en Excel y una prueba de una semana.",{"src":91,"card":92,"alt":234,"width":94,"height":95},"Código en una pantalla, ilustración de cómo elegir entre herramientas de feedback visual web",[236,168,237,203],"herramientas de feedback visual","feedback visual",{"path":239,"title":240,"description":241,"date":88,"modified":89,"draft":9,"locale":135,"category":11,"image":242,"translationKey":246,"tags":247,"readingTime":60},"\u002Fes\u002Fblog\u002Fpruebas-de-aceptacion-uat-web","Pruebas de aceptación de usuario (UAT): ejemplos y plantilla","Qué son las pruebas de aceptación de usuario (UAT), diferencias con el QA, ejemplos de escenarios, checklist para webs y plantillas gratis en Excel y Word.",{"src":243,"card":244,"alt":245,"width":94,"height":95},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback-400x250.jpg","Cliente haciendo pruebas de aceptación UAT de su nueva web frente al ordenador","uat",[248,249,250,251],"pruebas de aceptación","pruebas de aceptación de usuario","plan de pruebas de aceptación","ejemplo pruebas de aceptación",{"path":253,"title":254,"description":255,"date":88,"modified":89,"draft":9,"locale":135,"category":11,"image":256,"translationKey":258,"tags":259,"readingTime":102},"\u002Fes\u002Fblog\u002Fque-es-el-feedback-visual","Qué es el feedback visual y por qué agiliza tus proyectos web","Qué es el feedback visual: comentarios sobre la propia web con capturas marcadas, vídeo o notas. Tipos, ventajas, ejemplos y qué pedirle a una herramienta.",{"src":122,"card":123,"alt":257,"width":94,"height":95},"Diseñador web revisando el feedback visual sobre una interfaz","visual-feedback",[237,168,260,203],"capturas anotadas",{"path":262,"title":263,"description":264,"date":265,"modified":89,"draft":9,"locale":10,"category":77,"image":266,"translationKey":211,"tags":268,"readingTime":102},"\u002Fblog\u002Fsupercharge-your-workflow-with-the-notion-bug-tracker-extension","Notion Bug Tracker Template (Free) for Website Projects","Free Notion bug tracker template for website projects: import the CSV, set up the properties and board views, and send client feedback into Notion.","2025-04-24T16:17:44+00:00",{"src":108,"card":109,"alt":267,"width":111,"height":94},"Team organizing website bugs and client feedback in a Notion bug tracker",[269,270,271,272],"notion bug tracker template","notion issue tracker template","bug tracking","website feedback",{"path":274,"title":275,"description":276,"date":277,"modified":89,"draft":9,"locale":10,"category":11,"image":278,"translationKey":246,"tags":280,"readingTime":18},"\u002Fblog\u002Fuser-acceptance-testing-in-software-development","User Acceptance Testing (UAT): Template, Checklist & Examples","What user acceptance testing is, UAT vs QA, test scenario examples, a UAT checklist for websites and free templates: Excel test plan and Word sign-off form.","2023-09-28T17:32:27+00:00",{"src":243,"card":244,"alt":279,"width":94,"height":95},"Client doing user acceptance testing on a new website at his desk",[281,282,283,284],"user acceptance testing","UAT testing","user acceptance testing template","user acceptance testing checklist for website",{"path":286,"title":287,"description":288,"date":289,"modified":89,"draft":9,"locale":10,"category":220,"image":290,"translationKey":223,"tags":292,"readingTime":18},"\u002Fblog\u002Fbug-tracking-tools-free","Free Bug Tracking Tools for Web Teams (2026 Comparison)","Free bug tracking tools compared for web teams: the free plans of Jira, Trello, ClickUp, Notion, Asana, monday.com and Wrike, plus a free bug tracking spreadsheet.","2023-09-21T16:56:47+00:00",{"src":174,"card":175,"alt":291,"width":94,"height":95},"Team at a computer reviewing issues in a free bug tracking tool",[293,226,294,295],"free bug tracking tools","bug tracking spreadsheet","issue tracking",{"path":297,"title":298,"description":299,"date":300,"modified":89,"draft":9,"locale":10,"category":11,"image":301,"translationKey":189,"tags":303,"readingTime":102},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report","Bug Report Template (Free Excel, Word & Google Sheets) + Examples","Free bug report template for Excel, Google Sheets and Word, with a good and a bad bug report example and the fields that matter for website bugs.","2023-09-11T14:43:18+00:00",{"src":91,"card":92,"alt":302,"width":94,"height":95},"JavaScript code on a screen, illustrating how to write a bug report for a website",[304,305,306,294],"bug report template","bug report example","how to write a bug report",{"path":308,"title":309,"description":310,"date":311,"modified":89,"draft":9,"locale":10,"category":77,"image":312,"translationKey":163,"tags":314,"readingTime":102},"\u002Fblog\u002F1-way-to-get-annotated-screengrabs-into-asana","Asana Bug Tracking: Free Template and Annotated Screenshots","Asana bug tracking for website projects: a free CSV template, five ways to get annotated screenshots into tasks, and automatic tasks from client feedback.","2023-09-11T11:56:04+00:00",{"src":91,"card":92,"alt":313,"width":94,"height":95},"Annotated screenshots of a website being turned into Asana tasks",[315,316,317,272],"asana bug tracking","asana bug tracking template","annotated screenshots",{"path":319,"title":320,"description":321,"date":322,"modified":89,"draft":9,"locale":10,"category":11,"image":323,"translationKey":177,"tags":325,"readingTime":49},"\u002Fblog\u002Fspeed-up-qa-testing","Website QA Checklist: 70+ Checks Before Launch (Free Template)","A website QA checklist with 70+ checks by area (forms, links, devices, browsers, speed, SEO, accessibility, WordPress), plus a free Excel and Google Sheets template.","2023-08-19T11:32:36+00:00",{"src":174,"card":175,"alt":324,"width":94,"height":95},"Person running a website QA checklist on a laptop before launch",[326,327,328,329],"website QA checklist","website testing checklist","website qa checklist template excel","wordpress website testing checklist",{"path":331,"title":332,"description":333,"date":334,"modified":89,"draft":9,"locale":10,"category":11,"image":335,"translationKey":258,"tags":337,"readingTime":102},"\u002Fblog\u002Fvisual-feedback-faster-bug-testing","What Is Visual Feedback? A Guide for Web Teams","What is visual feedback? Feedback given on the website itself with marked-up screenshots, video or pinned comments. Types, examples and a tool checklist.","2023-08-09T17:41:00+00:00",{"src":122,"card":123,"alt":336,"width":94,"height":95},"Web designer reviewing visual feedback on a website interface",[338,100,317,272],"visual feedback",{"path":340,"title":341,"description":342,"date":343,"modified":89,"draft":9,"locale":10,"category":11,"image":344,"translationKey":140,"tags":346,"readingTime":83},"\u002Fblog\u002Fscreen-grab-annotation-apps","How to Annotate a Screenshot of a Website (Mac, Windows & Online)","How to annotate a screenshot on Mac, Windows, online or in Chrome, how to capture a full web page, and how to mark up website screenshots so developers fix them.","2023-08-02T23:25:13+00:00",{"src":137,"card":138,"alt":345,"width":94,"height":95},"Person at a computer annotating website screenshots for a developer",[347,348,349,350],"annotate screenshot","annotate screenshot mac","annotate screenshot windows","annotate screenshot online",{"id":352,"title":6,"body":353,"category":11,"date":8,"description":7,"draft":9,"extension":910,"faq":911,"image":12,"locale":10,"meta":927,"modified":8,"navigation":928,"path":5,"readingTime":18,"seo":929,"seoTitle":930,"stem":931,"tags":932,"tldr":933,"translationKey":12,"__hash__":934},"blog\u002Fblog\u002Fbug-triage-process.md",{"type":354,"value":355,"toc":897},"minimark",[356,360,366,371,374,377,381,384,409,412,501,505,508,589,592,596,599,659,662,666,669,730,733,736,740,743,811,819,822,826,829,845,848,852,860,868,872,875,878,886,894],[357,358,359],"p",{},"A bug triage process is how a team turns a pile of new bug reports into a short, ordered list of work. Without one, a client review round produces forty messages in three days, half of them duplicates or change requests, and the developer fixes whatever is at the top of the inbox. The steps, the meeting agenda and the free Word template below give every report a decision, and every accepted bug a severity, a priority and an owner.",[361,362],"template-download",{"files":363,"text":364,"title":365},"Word|\u002Ftemplates\u002Fbug-triage-meeting-template.docx","Word document with a 30-minute agenda, prep and follow-up checklists, the questions to answer for every bug, the six possible decisions, the severity and priority matrix and a decisions log.","Free bug triage meeting template",[367,368,370],"h2",{"id":369},"what-is-bug-triage","What is bug triage?",[357,372,373],{},"Bug triage is the process of reviewing new bug reports to confirm them, rate their severity, set their priority and assign an owner, so the team always works on the bugs that matter most. The word comes from emergency medicine, where triage sorts patients by urgency before anyone is treated. In both cases the sorting and the treatment are separate jobs.",[357,375,376],{},"Triage doesn't fix anything. Its output is a decision for every report: accepted and scheduled, or closed with a reason. On a website project, that also means separating real bugs from requests for something new, which is where most of the time goes when clients are reviewing.",[367,378,380],{"id":379},"what-are-the-steps-of-the-bug-triage-process","What are the steps of the bug triage process?",[357,382,383],{},"Seven steps, in this order: collect, screen, reproduce, classify, rate severity, set priority, assign and reply. The first three can happen before any meeting; the last four are the decisions the meeting is for.",[385,386,387,391,394,397,400,403,406],"ol",{},[388,389,390],"li",{},"Collect every report in one place. Emails, chat messages and calls get turned into reports in the same list, or they never get triaged.",[388,392,393],{},"Screen. Split reports that contain several problems, link duplicates to the original, and send back anything without a page, steps or a screenshot.",[388,395,396],{},"Reproduce. Follow the steps on the reported browser and device. A bug nobody can reproduce gets a specific question to the reporter, not a guess.",[388,398,399],{},"Classify. Is it a bug (it doesn't work as agreed), a change request (the client wants something different) or not a bug at all (it works as designed)?",[388,401,402],{},"Rate severity: what the bug does to one person who runs into it, from critical to trivial.",[388,404,405],{},"Set priority: when it gets fixed, from severity plus the page, the number of people affected and the deadlines.",[388,407,408],{},"Assign and reply. Give it an owner and a target, and tell the reporter what happens next.",[357,410,411],{},"Every report leaves triage with one of six decisions:",[413,414,415,431],"table",{},[416,417,418],"thead",{},[419,420,421,425,428],"tr",{},[422,423,424],"th",{},"Decision",[422,426,427],{},"When",[422,429,430],{},"What happens next",[432,433,434,446,457,468,479,490],"tbody",{},[419,435,436,440,443],{},[437,438,439],"td",{},"Accept",[437,441,442],{},"Reproduced and in scope",[437,444,445],{},"Severity, priority, owner and target",[419,447,448,451,454],{},[437,449,450],{},"Duplicate",[437,452,453],{},"The same problem is already on the list",[437,455,456],{},"Link it to the original and close it",[419,458,459,462,465],{},[437,460,461],{},"Needs info",[437,463,464],{},"It can't be reproduced from the report",[437,466,467],{},"Ask the reporter one specific question; review it at the next triage",[419,469,470,473,476],{},[437,471,472],{},"Not a bug",[437,474,475],{},"It works as specified or as designed",[437,477,478],{},"Reply with the reason and close it",[419,480,481,484,487],{},[437,482,483],{},"Change request",[437,485,486],{},"A new or different feature, not a fault",[437,488,489],{},"Move it to the change request list for the client",[419,491,492,495,498],{},[437,493,494],{},"Won't fix",[437,496,497],{},"Real, but not worth fixing now",[437,499,500],{},"Write down why; close it or keep it as P4",[367,502,504],{"id":503},"who-should-attend-a-bug-triage-meeting","Who should attend a bug triage meeting?",[357,506,507],{},"Three roles are enough for most website projects: a triage lead who prepares the list and runs the meeting, a developer who can judge severity and the size of a fix, and the person who owns the schedule, usually the project manager or product owner, who sets priority. Everyone else joins only when their bugs are on the list.",[413,509,510,523],{},[416,511,512],{},[419,513,514,517,520],{},[422,515,516],{},"Role",[422,518,519],{},"What they bring",[422,521,522],{},"When they attend",[432,524,525,536,546,556,567,578],{},[419,526,527,530,533],{},[437,528,529],{},"Triage lead",[437,531,532],{},"Prepares the list, keeps time, records every decision",[437,534,535],{},"Always",[419,537,538,541,544],{},[437,539,540],{},"Developer",[437,542,543],{},"Confirms severity, estimates the fix, spots duplicates",[437,545,535],{},[419,547,548,551,554],{},[437,549,550],{},"Project manager or product owner",[437,552,553],{},"Sets priority against deadlines and the client's goals",[437,555,535],{},[419,557,558,561,564],{},[437,559,560],{},"Tester or QA",[437,562,563],{},"Reproduction details and the bugs they found",[437,565,566],{},"When their reports are on the list",[419,568,569,572,575],{},[437,570,571],{},"Designer",[437,573,574],{},"Whether a visual issue is a bug or the approved design",[437,576,577],{},"When there are layout or design reports",[419,579,580,583,586],{},[437,581,582],{},"Client",[437,584,585],{},"Business priorities and approval of change requests",[437,587,588],{},"For the top items, or through a summary afterwards",[357,590,591],{},"In small teams one person often holds two roles; a freelancer may hold all three. The roles still matter, because each one is a different question: is it real, how bad is it, and when does it get fixed.",[367,593,595],{"id":594},"how-often-should-you-triage-bugs","How often should you triage bugs?",[357,597,598],{},"Match the rhythm to how fast reports arrive. A pattern that works for most website projects:",[413,600,601,614],{},[416,602,603],{},[419,604,605,608,611],{},[422,606,607],{},"Project phase",[422,609,610],{},"Triage rhythm",[422,612,613],{},"Typical length",[432,615,616,627,637,648],{},[419,617,618,621,624],{},[437,619,620],{},"Client review round or pre-launch QA",[437,622,623],{},"Daily",[437,625,626],{},"15 to 30 minutes",[419,628,629,632,635],{},[437,630,631],{},"First weeks after launch",[437,633,634],{},"Two or three times a week",[437,636,626],{},[419,638,639,642,645],{},[437,640,641],{},"Live site in maintenance",[437,643,644],{},"Weekly",[437,646,647],{},"15 minutes",[419,649,650,653,656],{},[437,651,652],{},"A critical bug at any time",[437,654,655],{},"Immediately, without waiting for the meeting",[437,657,658],{},"As long as it takes",[357,660,661],{},"The last row is the exception that makes the rest work. A checkout that fails at 10am doesn't wait for Thursday's triage: whoever finds it escalates it at once, and the next triage only records the decision. Everything else waits for the meeting, which is what protects the developers from constant interruptions.",[367,663,665],{"id":664},"a-30-minute-bug-triage-meeting-agenda","A 30-minute bug triage meeting agenda",[357,667,668],{},"Spend the first five minutes on critical bugs, fifteen on new reports, five on open bugs whose priority may have changed and the last five on open questions and change requests. The agenda only fits in thirty minutes if the triage lead does the screening beforehand.",[413,670,671,684],{},[416,672,673],{},[419,674,675,678,681],{},[422,676,677],{},"Minutes",[422,679,680],{},"Item",[422,682,683],{},"Output",[432,685,686,697,708,719],{},[419,687,688,691,694],{},[437,689,690],{},"0 to 5",[437,692,693],{},"Critical first: new bugs that look critical, and the status of every open P1",[437,695,696],{},"An owner and a plan for each P1",[419,698,699,702,705],{},[437,700,701],{},"5 to 20",[437,703,704],{},"New bugs, one by one: confirm, rate severity, set priority, assign",[437,706,707],{},"A decision for every new bug",[419,709,710,713,716],{},[437,711,712],{},"20 to 25",[437,714,715],{},"Priority changes: open bugs whose deadline, traffic or client plans changed",[437,717,718],{},"Updated priorities",[419,720,721,724,727],{},[437,722,723],{},"25 to 30",[437,725,726],{},"Needs info and change requests: who asks what, what goes to the client",[437,728,729],{},"Questions sent, change requests listed",[357,731,732],{},"Before the meeting, the triage lead pulls new reports into one list, merges duplicates, sends incomplete reports back and tries to reproduce anything that looks critical. After it, every bug is updated in the tracker, reporters get their answers and the client gets the change requests as a separate list. The template has both as checklists, plus a decisions log for overrides.",[357,734,735],{},"One rule keeps the meeting short: decide, don't solve. As soon as two people start discussing how to fix a bug, note the owner and move on.",[367,737,739],{"id":738},"using-a-bug-triage-matrix","Using a bug triage matrix",[357,741,742],{},"A bug triage matrix crosses severity with business urgency and suggests a priority for each combination, so the team starts from a default instead of an argument. The template uses this one:",[413,744,745,761],{},[416,746,747],{},[419,748,749,752,755,758],{},[422,750,751],{},"Severity \u002F Urgency",[422,753,754],{},"High",[422,756,757],{},"Medium",[422,759,760],{},"Low",[432,762,763,776,788,800],{},[419,764,765,768,771,773],{},[437,766,767],{},"Critical",[437,769,770],{},"P1",[437,772,770],{},[437,774,775],{},"P2",[419,777,778,781,783,785],{},[437,779,780],{},"Major",[437,782,770],{},[437,784,775],{},[437,786,787],{},"P3",[419,789,790,793,795,797],{},[437,791,792],{},"Minor",[437,794,775],{},[437,796,787],{},[437,798,799],{},"P4",[419,801,802,805,807,809],{},[437,803,804],{},"Trivial",[437,806,775],{},[437,808,799],{},[437,810,799],{},[357,812,813,814,818],{},"Severity comes from the bug: does it take the site down, break a main feature, look wrong or only bother a perfectionist? Urgency comes from the context: a key page or a fixed date is high, an old page few people visit is low. The definitions of each level, website examples and an Excel version that fills in the suggested priority for you are in our guide to ",[815,816,56],"a",{"href":817},"\u002Fblog\u002Fbug-severity-vs-priority\u002F",".",[357,820,821],{},"The matrix suggests; the meeting decides. A typo in the client's company name comes out as P2 and often goes to P1, because the client reviews the site tomorrow and the fix takes two minutes. Write the reason in the decisions log. If the same override keeps appearing, change the matrix.",[367,823,825],{"id":824},"bugs-change-requests-and-works-as-designed","Bugs, change requests and \"works as designed\"",[357,827,828],{},"On client website projects, the hardest part of triage is deciding what counts as a bug at all. \"The logo should be bigger\" is a change request. \"The menu is in the wrong order\" depends on what was approved. \"The form doesn't send\" is a bug. The reference is always the agreed scope: the approved design, the specification or the acceptance criteria.",[830,831,832,839,842],"ul",{},[388,833,834,835,838],{},"When a report matches the agreed design but the client wants something else, it is a change request. Log it on a separate list, with the page and the screenshot, and send it to the client for approval and, where it applies, a quote. The ",[815,836,25],{"href":837},"\u002Fblog\u002Fwebsite-change-request-form\u002F"," has a form and a log for that list.",[388,840,841],{},"When the design never covered the case (a tablet width nobody mocked up, a 40-character product name), treat it as a bug unless fixing it changes the design.",[388,843,844],{},"When the team disagrees, ask the designer before the client. Most \"is this a bug?\" questions are answered by the approved mockups.",[357,846,847],{},"Keeping change requests out of the bug list does two things: it keeps the bug count honest, and it turns unpaid scope into a visible list the client can approve.",[367,849,851],{"id":850},"running-triage-in-jira-or-another-tracker","Running triage in Jira or another tracker",[357,853,854,855,859],{},"Give untriaged reports a marker and triage from a saved view. In Jira that can be a needs-triage label or a separate status at the start of the workflow, a filter for open bugs without a priority, and severity labels or a custom field for the result. Our ",[815,856,858],{"href":857},"\u002Fblog\u002Fjira-bug-report-template\u002F","Jira bug report template"," has a CSV with severity labels, a description structure and two saved filters to start from.",[357,861,862,863,867],{},"The same idea works in any tool: a Trello list called \"To triage\", a ClickUp status, a monday.com group. What matters is that new reports land in one visible place and leave it only with a decision. If reports come from your website, they can arrive in that place on their own; the ",[815,864,866],{"href":865},"\u002Fbug-tracker-tool-integrations\u002F","integrations"," page lists the tools GiveFeedback.io sends them to.",[367,869,871],{"id":870},"getting-reports-that-are-ready-to-triage","Getting reports that are ready to triage",[357,873,874],{},"Screening and reproducing take most of the triage time, and most of that goes into missing information: which page, which browser, what the screen showed. Reports that arrive complete make the meeting short.",[876,877],"blog-cta",{},[357,879,880,881,885],{},"With ",[815,882,884],{"href":883},"\u002Fwebsite-annotation-tool\u002F","GiveFeedback.io",", clients and testers report from the website itself: they click a \"Give Feedback\" button, mark up a screenshot of the page and describe the problem, with no account. Each report arrives with the page URL, the browser and version, the operating system, the screen resolution and a log of the page's console messages, errors and failed requests, so the developer can often confirm severity from the report alone.",[357,887,888,889,893],{},"Reports land in a dashboard with Open, Resolved and Archived statuses, and can be created automatically in Jira, Trello, ClickUp, Asana, monday.com, Wrike or Notion, posted to Slack or Discord, or emailed. On paid plans the status syncs both ways with Jira, Trello, ClickUp, Asana, monday.com, Wrike, Slack and Discord, so a bug closed in the tracker is resolved in GiveFeedback.io too. If your developers use Claude Code, the ",[815,890,892],{"href":891},"\u002Fclaude-mcp-server\u002F","MCP server"," lets it list a project's reports and read each one in full, screenshot and console log included, which makes a quick first pass for duplicates before the meeting.",[357,895,896],{},"Print the agenda, book a recurring 30-minute slot for the next review round and send the first incomplete report back before the meeting starts. Two or three sessions in, the list that reaches the developers will be shorter, ordered and free of surprises.",{"title":898,"searchDepth":899,"depth":899,"links":900},"",2,[901,902,903,904,905,906,907,908,909],{"id":369,"depth":899,"text":370},{"id":379,"depth":899,"text":380},{"id":503,"depth":899,"text":504},{"id":594,"depth":899,"text":595},{"id":664,"depth":899,"text":665},{"id":738,"depth":899,"text":739},{"id":824,"depth":899,"text":825},{"id":850,"depth":899,"text":851},{"id":870,"depth":899,"text":871},"md",[912,915,918,921,924],{"question":913,"answer":914},"What is the difference between bug triage and bug prioritization?","Prioritization is one step of triage. Triage starts earlier, by checking that a report is a real, reproducible and unique bug rather than a duplicate or a change request, and it ends later, with an owner, a target and a reply to the reporter. Prioritization is only the part where the team decides when a confirmed bug gets fixed.",{"question":916,"answer":917},"What should you do with bugs that can't be reproduced?","Mark them as needing information and ask the reporter one specific question: which page, which browser, what they clicked just before. Keep them on the list for one or two more triage sessions. If nobody can reproduce the bug and it hasn't come back, close it with a note explaining what was tried, so it can be reopened if it happens again.",{"question":919,"answer":920},"Should the client attend bug triage meetings?","Usually not the whole meeting. Most of triage is technical sorting the client doesn't need to sit through. Agree the top priorities with them instead: send a short summary after triage with the bugs being fixed first, the questions that need their answer and the change requests that need their approval. Invite them only when a decision depends on their business, such as a launch date.",{"question":922,"answer":923},"What is a bug triage matrix?","A grid that crosses bug severity with business urgency to suggest a default priority for each combination, for example a critical bug on a key page giving priority one. It lets the meeting start from a suggestion instead of a debate. The team can override any suggestion, but should write down why, so the matrix improves as the project goes on.",{"question":925,"answer":926},"How long should a bug triage meeting take?","Thirty minutes is a good ceiling for most website projects, and fifteen is often enough during a busy review round with daily triage. If it keeps running over, the preparation is missing: duplicates not merged, incomplete reports not sent back, critical bugs not reproduced beforehand. Discussing how to fix a bug belongs after the meeting, between the people doing the fix.",{},true,{"title":6,"description":7},"Bug Triage Process: Steps, Meeting Agenda, Checklist","blog\u002Fbug-triage-process",[14,15,16,17],"Bug triage is the regular review where a team takes every new bug report and decides what happens to it: accept it, or close it as a duplicate, not a bug or a change request; then rate its severity, set its priority and give it an owner. Keep it short and frequent: a triage lead prepares the list, a developer and whoever owns the schedule decide, and every reporter hears back.","PY-XoL9re2uBbLH356nFKiyIr_GhwcfPvgqp0s4UJU4",1795016127635]