[{"data":1,"prerenderedAt":924},["ShallowReactive",2],{"blog-posts":3,"post-\u002Fblog\u002Fbug-severity-vs-priority":321},[4,19,30,41,53,72,86,101,116,127,139,153,165,175,186,199,208,222,231,243,255,266,277,288,300,309],{"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\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",false,"en","guides",null,[14,15,16,17],"website feedback form questions","website feedback form template","website feedback form examples","website feedback survey questions",11,{"path":20,"title":21,"description":22,"date":23,"modified":23,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":24,"readingTime":29},"\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",[25,26,27,28],"bug severity vs priority","bug severity levels","bug severity matrix","severity and priority examples",10,{"path":31,"title":32,"description":33,"date":34,"modified":34,"draft":9,"locale":10,"category":11,"image":12,"translationKey":12,"tags":35,"readingTime":40},"\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",[36,37,38,39],"website handover checklist","website handover document template","website handover process","web agency",12,{"path":42,"title":43,"description":44,"date":45,"modified":45,"draft":9,"locale":10,"category":46,"image":12,"translationKey":12,"tags":47,"readingTime":52},"\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",[48,49,50,51],"claude code fix bugs","claude code mcp","ai bug fixing","bug report",7,{"path":54,"title":55,"description":56,"date":57,"modified":58,"draft":9,"locale":10,"category":11,"image":59,"translationKey":65,"tags":66,"readingTime":71},"\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":60,"card":61,"alt":62,"width":63,"height":64},"\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",[67,68,69,70],"best website feedback tool","website feedback tool free","visual website feedback tool","client feedback",8,{"path":73,"title":74,"description":75,"date":57,"modified":58,"draft":9,"locale":10,"category":46,"image":76,"translationKey":81,"tags":82,"readingTime":71},"\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":77,"card":78,"alt":79,"width":80,"height":63},"\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",[83,84,85,39],"client approval process","website sign off","revision rounds",{"path":87,"title":88,"description":89,"date":57,"modified":58,"draft":9,"locale":10,"category":11,"image":90,"translationKey":94,"tags":95,"readingTime":100},"\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":91,"card":92,"alt":93,"width":63,"height":64},"\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",[96,97,98,99],"client feedback on website","website feedback examples","client feedback examples","website review process",9,{"path":102,"title":103,"description":104,"date":57,"modified":58,"draft":9,"locale":105,"category":11,"image":106,"translationKey":110,"tags":111,"readingTime":52},"\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":107,"card":108,"alt":109,"width":63,"height":64},"\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",[112,113,114,115],"anotar capturas de pantalla","captura de pantalla","anotar captura en Mac","anotar captura en Windows",{"path":117,"title":118,"description":119,"date":57,"modified":58,"draft":9,"locale":105,"category":46,"image":120,"translationKey":81,"tags":122,"readingTime":71},"\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":77,"card":78,"alt":121,"width":80,"height":63},"Dos personas revisan un documento con un bolígrafo antes de la aprobación del cliente en un proyecto web",[123,124,125,126],"aprobación del cliente","rondas de revisión","presupuesto web","agencia web",{"path":128,"title":129,"description":130,"date":57,"modified":58,"draft":9,"locale":105,"category":46,"image":131,"translationKey":133,"tags":134,"readingTime":100},"\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":60,"card":61,"alt":132,"width":63,"height":64},"Capturas anotadas de una web convertidas en tareas de Asana","asana",[135,136,137,138],"capturas anotadas en Asana","plantilla Asana","gestión de bugs","feedback web",{"path":140,"title":141,"description":142,"date":57,"modified":58,"draft":9,"locale":105,"category":11,"image":143,"translationKey":147,"tags":148,"readingTime":40},"\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":144,"card":145,"alt":146,"width":63,"height":64},"\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",[149,150,151,152],"checklist web","checklist QA web","pruebas web","lanzamiento web",{"path":154,"title":155,"description":156,"date":57,"modified":58,"draft":9,"locale":105,"category":11,"image":157,"translationKey":159,"tags":160,"readingTime":100},"\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":60,"card":61,"alt":158,"width":63,"height":64},"Código JavaScript en una pantalla, ilustrando cómo escribir un informe de bugs de una web","bug-report",[161,162,163,164],"plantilla de reporte de errores","reporte de errores","informe de bugs","ejemplo de reporte de errores",{"path":166,"title":167,"description":168,"date":57,"modified":58,"draft":9,"locale":105,"category":11,"image":169,"translationKey":94,"tags":171,"readingTime":100},"\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":91,"card":92,"alt":170,"width":63,"height":64},"Diseñador web en su mesa revisando el feedback de clientes sobre una web",[172,173,138,174],"cómo pedir feedback a un cliente","feedback de clientes","revisión de una web",{"path":176,"title":177,"description":178,"date":57,"modified":58,"draft":9,"locale":105,"category":46,"image":179,"translationKey":181,"tags":182,"readingTime":71},"\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":77,"card":78,"alt":180,"width":80,"height":63},"Equipo organizando bugs y feedback de clientes de una web en Notion","notion",[183,184,185,138],"bugs en Notion","plantilla Notion","seguimiento de bugs",{"path":187,"title":188,"description":189,"date":57,"modified":58,"draft":9,"locale":105,"category":190,"image":191,"translationKey":193,"tags":194,"readingTime":100},"\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":144,"card":145,"alt":192,"width":63,"height":64},"Equipo revisando incidencias en una herramienta gratis de seguimiento de bugs","free-bug-tracking",[195,196,197,198],"herramientas gratis seguimiento de bugs","bug tracker","gestión de incidencias","hoja de seguimiento de bugs",{"path":200,"title":201,"description":202,"date":57,"modified":58,"draft":9,"locale":105,"category":11,"image":203,"translationKey":65,"tags":205,"readingTime":100},"\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":60,"card":61,"alt":204,"width":63,"height":64},"Código en una pantalla, ilustración de cómo elegir entre herramientas de feedback visual web",[206,138,207,173],"herramientas de feedback visual","feedback visual",{"path":209,"title":210,"description":211,"date":57,"modified":58,"draft":9,"locale":105,"category":11,"image":212,"translationKey":216,"tags":217,"readingTime":29},"\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":213,"card":214,"alt":215,"width":63,"height":64},"\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",[218,219,220,221],"pruebas de aceptación","pruebas de aceptación de usuario","plan de pruebas de aceptación","ejemplo pruebas de aceptación",{"path":223,"title":224,"description":225,"date":57,"modified":58,"draft":9,"locale":105,"category":11,"image":226,"translationKey":228,"tags":229,"readingTime":71},"\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":91,"card":92,"alt":227,"width":63,"height":64},"Diseñador web revisando el feedback visual sobre una interfaz","visual-feedback",[207,138,230,173],"capturas anotadas",{"path":232,"title":233,"description":234,"date":235,"modified":58,"draft":9,"locale":10,"category":46,"image":236,"translationKey":181,"tags":238,"readingTime":71},"\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":77,"card":78,"alt":237,"width":80,"height":63},"Team organizing website bugs and client feedback in a Notion bug tracker",[239,240,241,242],"notion bug tracker template","notion issue tracker template","bug tracking","website feedback",{"path":244,"title":245,"description":246,"date":247,"modified":58,"draft":9,"locale":10,"category":11,"image":248,"translationKey":216,"tags":250,"readingTime":100},"\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":213,"card":214,"alt":249,"width":63,"height":64},"Client doing user acceptance testing on a new website at his desk",[251,252,253,254],"user acceptance testing","UAT testing","user acceptance testing template","user acceptance testing checklist for website",{"path":256,"title":257,"description":258,"date":259,"modified":58,"draft":9,"locale":10,"category":190,"image":260,"translationKey":193,"tags":262,"readingTime":100},"\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":144,"card":145,"alt":261,"width":63,"height":64},"Team at a computer reviewing issues in a free bug tracking tool",[263,196,264,265],"free bug tracking tools","bug tracking spreadsheet","issue tracking",{"path":267,"title":268,"description":269,"date":270,"modified":58,"draft":9,"locale":10,"category":11,"image":271,"translationKey":159,"tags":273,"readingTime":71},"\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":60,"card":61,"alt":272,"width":63,"height":64},"JavaScript code on a screen, illustrating how to write a bug report for a website",[274,275,276,264],"bug report template","bug report example","how to write a bug report",{"path":278,"title":279,"description":280,"date":281,"modified":58,"draft":9,"locale":10,"category":46,"image":282,"translationKey":133,"tags":284,"readingTime":71},"\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":60,"card":61,"alt":283,"width":63,"height":64},"Annotated screenshots of a website being turned into Asana tasks",[285,286,287,242],"asana bug tracking","asana bug tracking template","annotated screenshots",{"path":289,"title":290,"description":291,"date":292,"modified":58,"draft":9,"locale":10,"category":11,"image":293,"translationKey":147,"tags":295,"readingTime":18},"\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":144,"card":145,"alt":294,"width":63,"height":64},"Person running a website QA checklist on a laptop before launch",[296,297,298,299],"website QA checklist","website testing checklist","website qa checklist template excel","wordpress website testing checklist",{"path":301,"title":302,"description":303,"date":304,"modified":58,"draft":9,"locale":10,"category":11,"image":305,"translationKey":228,"tags":307,"readingTime":71},"\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":91,"card":92,"alt":306,"width":63,"height":64},"Web designer reviewing visual feedback on a website interface",[308,69,287,242],"visual feedback",{"path":310,"title":311,"description":312,"date":313,"modified":58,"draft":9,"locale":10,"category":11,"image":314,"translationKey":110,"tags":316,"readingTime":52},"\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":107,"card":108,"alt":315,"width":63,"height":64},"Person at a computer annotating website screenshots for a developer",[317,318,319,320],"annotate screenshot","annotate screenshot mac","annotate screenshot windows","annotate screenshot online",{"id":322,"title":21,"body":323,"category":11,"date":23,"description":22,"draft":9,"extension":899,"faq":900,"image":12,"locale":10,"meta":916,"modified":23,"navigation":917,"path":20,"readingTime":29,"seo":918,"seoTitle":919,"stem":920,"tags":921,"tldr":922,"translationKey":12,"__hash__":923},"blog\u002Fblog\u002Fbug-severity-vs-priority.md",{"type":324,"value":325,"toc":886},"minimark",[326,330,336,341,344,355,444,447,451,454,514,517,521,524,598,607,611,614,687,690,693,697,700,703,716,719,776,779,782,786,789,800,808,812,815,832,839,843,846,849,857,861,864,867,875,883],[327,328,329],"p",{},"Bug severity vs priority is the difference between how bad a bug is and how soon it gets fixed. When a team keeps both in one field, the loudest \"urgent!!\" wins, a typo in a footer sits next to a broken checkout and nobody can explain why one was fixed before the other. The definitions, the website examples and the free matrix below give every bug two separate answers, with a written reason when they disagree.",[331,332],"template-download",{"files":333,"text":334,"title":335},"Excel|\u002Ftemplates\u002Fbug-severity-priority-matrix-template.xlsx","Excel with the matrix, four severity levels with website examples, priority levels mapped to Jira, and a bug log that suggests the priority of each bug (opens in Google Sheets: File > Import).","Free bug severity and priority matrix",[337,338,340],"h2",{"id":339},"what-is-the-difference-between-bug-severity-and-priority","What is the difference between bug severity and priority?",[327,342,343],{},"Bug severity is the degree of impact a bug has on the people using the site or the system behind it; bug priority is the order in which the team will fix it. Severity describes the bug. Priority describes a decision about the bug, and that decision depends on things the bug itself doesn't know: the launch date, the client's campaign, how many visitors use the page.",[327,345,346,347,354],{},"The ",[348,349,353],"a",{"href":350,"rel":351},"https:\u002F\u002Fglossary.istqb.org\u002Fen_US\u002Fterm\u002Fseverity",[352],"nofollow","ISTQB testing glossary"," draws the same line: severity is about the impact of a defect, priority about its business importance. In practice the two are set by different people, at different moments, with different information.",[356,357,358,374],"table",{},[359,360,361],"thead",{},[362,363,364,368,371],"tr",{},[365,366,367],"th",{},"Aspect",[365,369,370],{},"Severity",[365,372,373],{},"Priority",[375,376,377,389,400,411,422,433],"tbody",{},[362,378,379,383,386],{},[380,381,382],"td",{},"Question it answers",[380,384,385],{},"How bad is it?",[380,387,388],{},"How soon do we fix it?",[362,390,391,394,397],{},[380,392,393],{},"Based on",[380,395,396],{},"What the bug does to one person who hits it",[380,398,399],{},"Severity plus reach, deadlines, the client's goals and the cost of the fix",[362,401,402,405,408],{},[380,403,404],{},"Set by",[380,406,407],{},"Tester or developer (the reporter can suggest)",[380,409,410],{},"Project manager, product owner or team lead",[362,412,413,416,419],{},[380,414,415],{},"Changes over time",[380,417,418],{},"Rarely, only when you learn more about the bug",[380,420,421],{},"Often, as deadlines, traffic and plans change",[362,423,424,427,430],{},[380,425,426],{},"Typical scale",[380,428,429],{},"Critical, Major, Minor, Trivial",[380,431,432],{},"P1 to P4 (Highest to Low in Jira)",[362,434,435,438,441],{},[380,436,437],{},"Example",[380,439,440],{},"Checkout fails for every card: Critical",[380,442,443],{},"The sale starts tomorrow: P1, fix today",[327,445,446],{},"Keeping them apart turns an argument into two short conversations. Severity is a question of fact (\"does the form lose the message or not?\"), and it can be checked against the screenshot and the steps. Priority is a question of judgment (\"is this more important than the menu bug before Friday's review?\"), and it belongs to whoever owns the schedule.",[337,448,450],{"id":449},"bug-severity-levels-with-website-examples","Bug severity levels, with website examples",[327,452,453],{},"Four levels cover almost every team: critical, major, minor and trivial. Rate severity on what the bug does to one person who runs into it. How many people run into it, and when, belongs to priority; mixing reach into severity is what makes a crash on an old page and a crash in checkout look the same.",[356,455,456,468],{},[359,457,458],{},[362,459,460,462,465],{},[365,461,370],{},[365,463,464],{},"What it means",[365,466,467],{},"Website examples",[375,469,470,481,492,503],{},[362,471,472,475,478],{},[380,473,474],{},"Critical",[380,476,477],{},"The site is down, people can't complete a core task (buying, booking, sending a form, logging in) or data is lost or exposed, with no workaround",[380,479,480],{},"Checkout returns an error for every card; contact form submissions never arrive; one customer can see another customer's orders",[362,482,483,486,489],{},[380,484,485],{},"Major",[380,487,488],{},"A main feature fails or gives wrong results, or only works with a workaround most people won't find",[380,490,491],{},"The mobile menu doesn't open on iPhone; search returns no results; product prices show without tax",[362,493,494,497,500],{},[380,495,496],{},"Minor",[380,498,499],{},"Something works but looks wrong or is awkward; there is an easy workaround and no money or data at risk",[380,501,502],{},"The hero headline overlaps the image at 768px wide; a date shows in the wrong format; a form error says \"Error 422\"",[362,504,505,508,511],{},[380,506,507],{},"Trivial",[380,509,510],{},"Cosmetic only; nothing changes about what people can do",[380,512,513],{},"A typo in body copy; an icon 2px out of line; a button in a slightly wrong shade",[327,515,516],{},"Two rules keep the scale honest. Write one real example from your own projects next to each level, so new testers calibrate against something concrete. And reproduce before you rate: a \"critical\" bug that only happens with a browser extension installed usually isn't.",[337,518,520],{"id":519},"priority-levels-when-the-bug-gets-fixed","Priority levels: when the bug gets fixed",[327,522,523],{},"Priority says when, so define each level by what the team does, not by how anyone feels. Four levels map cleanly onto a website project's rhythm of review rounds, launch and maintenance.",[356,525,526,540],{},[359,527,528],{},[362,529,530,532,534,537],{},[365,531,373],{},[365,533,464],{},[365,535,536],{},"Example target",[365,538,539],{},"In Jira",[375,541,542,556,570,584],{},[362,543,544,547,550,553],{},[380,545,546],{},"P1",[380,548,549],{},"Fix now and stop other work: a hotfix on a live site, or a blocker for launch or the next client review",[380,551,552],{},"Same day",[380,554,555],{},"Highest",[362,557,558,561,564,567],{},[380,559,560],{},"P2",[380,562,563],{},"Fix before launch, or in the current sprint or week",[380,565,566],{},"This week",[380,568,569],{},"High",[362,571,572,575,578,581],{},[380,573,574],{},"P3",[380,576,577],{},"Schedule for the next sprint or the next maintenance batch",[380,579,580],{},"Next sprint",[380,582,583],{},"Medium",[362,585,586,589,592,595],{},[380,587,588],{},"P4",[380,590,591],{},"Backlog: fix when there's time, or close as won't fix at the next review",[380,593,594],{},"Review monthly",[380,596,597],{},"Low",[327,599,600,601,606],{},"The targets are examples; agree your own and write them down, because a P1 that waits three days teaches everyone to ignore the scale. The Jira column uses Jira's ",[348,602,605],{"href":603,"rel":604},"https:\u002F\u002Fsupport.atlassian.com\u002Fjira-cloud-administration\u002Fdocs\u002Fwhat-are-issue-statuses-priorities-and-resolutions\u002F",[352],"default priorities",", Highest to Lowest, which a Jira admin can rename or extend.",[337,608,610],{"id":609},"severity-and-priority-examples-when-they-disagree","Severity and priority examples: when they disagree",[327,612,613],{},"Most of the time the two move together: a broken checkout is critical and gets fixed first, a misaligned icon is trivial and waits. The cases worth discussing are the other two, where a severe bug can wait and a trivial one can't.",[356,615,616,632],{},[359,617,618],{},[362,619,620,623,626,629],{},[365,621,622],{},"Combination",[365,624,625],{},"Website example",[365,627,628],{},"Typical priority",[365,630,631],{},"Why",[375,633,634,647,660,674],{},[362,635,636,639,642,644],{},[380,637,638],{},"High severity, high priority",[380,640,641],{},"Checkout fails for every card the day before a sale starts",[380,643,546],{},[380,645,646],{},"Revenue stops and a date depends on it",[362,648,649,652,655,657],{},[380,650,651],{},"High severity, low priority",[380,653,654],{},"A 2019 events archive page returns a server error",[380,656,574],{},[380,658,659],{},"The page is broken, but almost nobody visits it and nothing links to it",[362,661,662,665,668,671],{},[380,663,664],{},"Low severity, high priority",[380,666,667],{},"The client's company name is misspelled in the home page headline",[380,669,670],{},"P1 or P2",[380,672,673],{},"Cosmetic, but it's the first thing the client and every visitor read",[362,675,676,679,682,684],{},[380,677,678],{},"Low severity, low priority",[380,680,681],{},"Footer icons are 2px out of line at one tablet width",[380,683,588],{},[380,685,686],{},"Nobody is stopped from doing anything",[327,688,689],{},"The misspelled company name is the classic case. No feature is broken, so its severity is trivial. But the client reviews the site tomorrow, the fix takes two minutes and leaving it signals carelessness on every page view, so it jumps the queue. The archive error is the reverse: anyone who opens that page sees nothing at all, yet fixing it this week would delay fixes that affect real visitors, so it gets scheduled rather than ignored.",[327,691,692],{},"Recording both values is what keeps the second case safe. A P3 with severity Major is visibly different from a P3 with severity Trivial, and it gets picked up once the launch is out of the way.",[337,694,696],{"id":695},"how-does-a-bug-severity-matrix-work","How does a bug severity matrix work?",[327,698,699],{},"A bug severity matrix is a grid that crosses severity with a second factor, usually business urgency, so that each combination suggests a default priority. The tester's rating and the business context meet in one cell, and the team starts triage from a suggestion instead of a blank field.",[327,701,702],{},"Business urgency needs its own three levels, written down like severity:",[704,705,706,710,713],"ul",{},[707,708,709],"li",{},"High: a key page or flow (home, checkout, contact, booking, login), most visitors, the client's brand, or a date that can't move.",[707,711,712],{},"Medium: a page or feature people use regularly, with a workaround and no deadline depending on it this week.",[707,714,715],{},"Low: few people affected, such as an old page, an unusual device or browser, or admin screens only.",[327,717,718],{},"The matrix in the template uses these defaults:",[356,720,721,734],{},[359,722,723],{},[362,724,725,728,730,732],{},[365,726,727],{},"Severity \u002F Urgency",[365,729,569],{},[365,731,583],{},[365,733,597],{},[375,735,736,746,756,766],{},[362,737,738,740,742,744],{},[380,739,474],{},[380,741,546],{},[380,743,546],{},[380,745,560],{},[362,747,748,750,752,754],{},[380,749,485],{},[380,751,546],{},[380,753,560],{},[380,755,574],{},[362,757,758,760,762,764],{},[380,759,496],{},[380,761,560],{},[380,763,574],{},[380,765,588],{},[362,767,768,770,772,774],{},[380,769,507],{},[380,771,560],{},[380,773,588],{},[380,775,588],{},[327,777,778],{},"In the Excel file, the Bug log sheet reads this grid: pick a severity and an urgency from the dropdowns and the Suggested priority column fills itself in. Change any cell on the Matrix sheet and every suggestion follows, so the grid can reflect your own rules.",[327,780,781],{},"The matrix suggests; a person decides. Next to the suggestion there is a Final priority column and a \"Reason if different\" column. In the example rows, the misspelled company name comes out as P2 from the matrix and is overridden to P1 with the reason \"client reviews the site tomorrow; two-minute fix\". Overrides with a written reason are healthy. Overrides without one, every week, mean the matrix needs adjusting.",[337,783,785],{"id":784},"who-sets-severity-and-who-sets-priority","Who sets severity and who sets priority?",[327,787,788],{},"The person closest to the bug rates severity, and the person who owns the schedule sets priority. On a website project that usually splits like this:",[704,790,791,794,797],{},[707,792,793],{},"The reporter (client, tester, colleague) describes what happened and what it stopped them doing. They can suggest a severity, but they don't set it.",[707,795,796],{},"The tester or developer reproduces the bug and confirms the severity.",[707,798,799],{},"The project manager, product owner or team lead sets priority during triage, and for client work agrees the top items with the client.",[327,801,802,803,807],{},"Clients deserve a note of their own. To a client, the bug they just found is the most important one, so \"urgent\" in a client email tells you about their mood, not the bug's severity. Ask what they were trying to do and whether it stops them or their customers, rate it yourself, and show them the priority you gave it. A client who sees their typo listed as P1 for tomorrow rarely argues about the server error on an old page staying at P3. Our guide on ",[348,804,806],{"href":805},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report\u002F","what to put in a bug report"," covers the questions to ask so the report carries the facts severity depends on.",[337,809,811],{"id":810},"common-mistakes-with-severity-and-priority","Common mistakes with severity and priority",[327,813,814],{},"Most problems come from treating the two fields as one, or from never writing down what the levels mean:",[704,816,817,820,823,826,829],{},[707,818,819],{},"One field for both. The team can no longer tell \"bad but rare\" from \"minor but visible\", and the reporter's adjective decides the order.",[707,821,822],{},"Everything is critical. If most open bugs are P1, the scale has stopped meaning anything; re-rate the list against the written definitions.",[707,824,825],{},"Reach inside severity. \"Only one user hit it\" lowers the priority, not the severity: the next user who hits it gets the same broken page.",[707,827,828],{},"Priority set once and never revisited. A P3 before launch can become P1 the week a campaign sends traffic to that page.",[707,830,831],{},"Rating without evidence. Severity arguments are usually missing-information arguments; a screenshot, the URL and the browser end most of them.",[327,833,834,835,838],{},"If you test a site before launch with a checklist, rate each failed check the same way; the ",[348,836,296],{"href":837},"\u002Fblog\u002Fspeed-up-qa-testing\u002F"," has a notes column that works well for it.",[337,840,842],{"id":841},"severity-and-priority-in-jira-and-other-trackers","Severity and priority in Jira and other trackers",[327,844,845],{},"Jira has a Priority field built in, with Highest, High, Medium, Low and Lowest as defaults, but no Severity field, so teams add a custom select field with Critical, Major, Minor and Trivial or use labels such as severity-critical. Map the template's P1 to P4 onto Highest to Low, and keep Lowest unused or for \"won't fix unless someone asks again\".",[327,847,848],{},"In trackers with no severity concept at all, one label or tag per level does the job, as long as everyone uses the same four words. Whatever the tool, set both values when the bug is triaged, not when it's reported: the reporter rarely has the context for priority.",[327,850,851,852,856],{},"If client reports reach Jira through ",[348,853,855],{"href":854},"\u002Fjira-bug-tracking-tool\u002F","the GiveFeedback.io Jira integration",", each one arrives as an issue with the report's title as the summary, the client's description, the page URL and the browser details, and the annotated screenshot attached. You add the priority, the severity field or label and the assignee in Jira as usual.",[337,858,860],{"id":859},"how-do-you-rate-severity-faster","How do you rate severity faster?",[327,862,863],{},"Give whoever triages the evidence up front. Most of the time spent rating a bug goes into finding out what happened: which page, which browser, what the screen showed, whether an error appeared in the console. When the report already contains that, rating severity takes seconds.",[865,866],"blog-cta",{},[327,868,869,870,874],{},"That is what ",[348,871,873],{"href":872},"\u002Fwebsite-annotation-tool\u002F","GiveFeedback.io"," is for. Clients and testers click a \"Give Feedback\" button on the site, mark up a screenshot of what they see and write what happened, without creating an account. Every 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. A \"checkout broken\" report with a red error in its console log and a failed payment request is easy to rate Critical; the same words with a clean log and a screenshot of a slow spinner point somewhere else.",[327,876,877,878,882],{},"Reports land in a dashboard with Open, Resolved and Archived statuses, or go straight to Jira, Trello, ClickUp, Asana, monday.com, Wrike, Notion, Slack, Discord or email. The Free plan covers 5 projects and 50 feedback reports; ",[348,879,881],{"href":880},"\u002Fpricing\u002F","pricing"," has the rest.",[327,884,885],{},"Write your four severity definitions this week, put a real example from your last project next to each, and run the next triage from the matrix. Within a couple of review rounds, \"why was this fixed first?\" becomes a question with a written answer.",{"title":887,"searchDepth":888,"depth":888,"links":889},"",2,[890,891,892,893,894,895,896,897,898],{"id":339,"depth":888,"text":340},{"id":449,"depth":888,"text":450},{"id":519,"depth":888,"text":520},{"id":609,"depth":888,"text":610},{"id":695,"depth":888,"text":696},{"id":784,"depth":888,"text":785},{"id":810,"depth":888,"text":811},{"id":841,"depth":888,"text":842},{"id":859,"depth":888,"text":860},"md",[901,904,907,910,913],{"question":902,"answer":903},"Can a bug have high severity and low priority?","Yes. A bug can break something completely and still wait, if almost nobody runs into it: a server error on an old archive page that nothing links to, or a crash in a feature that hasn't launched yet. It is severe for whoever hits it, but bugs that block more people or a deadline come first. Record both values so the bug isn't forgotten once the busy period is over.",{"question":905,"answer":906},"Who decides the priority of a bug?","The person who owns the schedule: a project manager, product owner or team lead, usually during triage. They start from the severity the tester or developer gave and add what the bug can't tell them on its own: deadlines, how many visitors use the page, what the client cares about and how long the fix takes. On client projects, agree the top priorities with the client.",{"question":908,"answer":909},"How many bug severity levels should a team use?","Four is enough for most teams: critical, major, minor and trivial. Fewer levels make the choice quick and stop people arguing over the difference between level four and level five. A written definition with a real example for each level matters more than the number, because it is what makes two testers rate the same bug the same way.",{"question":911,"answer":912},"Does Jira have a severity field?","Not by default. Jira has a Priority field whose default values are Highest, High, Medium, Low and Lowest, and admins can rename them or add more. For severity, teams add a custom select field with their own levels or use a label such as severity-major. Keeping the two apart lets priority change during the project without losing the original severity.",{"question":914,"answer":915},"Should clients set the severity of the bugs they report?","Let them describe the impact in their own words instead of picking a level. Clients tend to mark everything as urgent, which makes the field meaningless. Ask what they were trying to do, what happened and whether it stops them or their customers. Then the team sets the severity, and the top priorities are agreed with the client at the next review.",{},true,{"title":21,"description":22},"Bug Severity vs Priority: Examples and Free Matrix","blog\u002Fbug-severity-vs-priority",[25,26,27,28],"Severity is how badly a bug hurts the person who runs into it; priority is how soon the team will fix it. The tester or developer rates severity from the bug itself, and the project manager or product owner sets priority from severity plus business context: which page, how many people, which deadline. They usually move together, but a typo in the client's company name can be trivial in severity and still top priority.","4O-GGSJACw3NlSj4nC5HovxFmo3FyVeL_REOktTVs-U",1794242332766]