[{"data":1,"prerenderedAt":613},["ShallowReactive",2],{"blog-posts":3,"post-\u002Fblog\u002Fwhat-to-put-in-a-bug-report":177},[4,19,30,39,49,55,62,71,78,84,91,99,105,114,121,128,135,142,149,156,163,170],{"path":5,"title":6,"description":7,"date":8,"modified":9,"locale":10,"category":11,"image":12,"translationKey":18},"\u002Fblog\u002Fbest-website-feedback-tools","How to Choose a Website Feedback Tool (2026 Checklist)","How to choose the best website feedback tool in 2026: tool types, a 12-point checklist, a free scoring template and a one-week client trial plan.","2026-10-07T09:00:00+00:00","2026-10-08T09:00:00+00:00","en","guides",{"src":13,"card":14,"alt":15,"width":16,"height":17},"\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",{"path":20,"title":21,"description":22,"date":8,"modified":8,"locale":10,"category":23,"image":24,"translationKey":29},"\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 contract clause, a sign-off email template and a checklist you can reuse.","workflow",{"src":25,"card":26,"alt":27,"width":28,"height":16},"\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",{"path":31,"title":32,"description":33,"date":8,"modified":8,"locale":10,"category":11,"image":34,"translationKey":38},"\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: compare 5 methods, run a clean review round step by step, and copy our sample briefing email for clients.",{"src":35,"card":36,"alt":37,"width":16,"height":17},"\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",{"path":40,"title":41,"description":42,"date":8,"modified":8,"locale":43,"category":11,"image":44,"translationKey":48},"\u002Fes\u002Fblog\u002Fanotar-capturas-de-pantalla-web","Cómo anotar capturas de pantalla de una web (y enviarlas)","Aprende a anotar capturas de pantalla de una web con Recortes, Markup, el navegador, apps dedicadas o un widget de feedback. Comparativa, precios y ejemplos.","es",{"src":45,"card":46,"alt":47,"width":16,"height":17},"\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 en un ordenador anotando capturas de pantalla de una web para el desarrollador","screenshot-annotation",{"path":50,"title":51,"description":52,"date":8,"modified":8,"locale":43,"category":23,"image":53,"translationKey":29},"\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 listo para copiar y una checklist.",{"src":25,"card":26,"alt":54,"width":28,"height":16},"Dos personas revisan un documento con un bolígrafo antes de la aprobación del cliente en un proyecto web",{"path":56,"title":57,"description":58,"date":8,"modified":8,"locale":43,"category":23,"image":59,"translationKey":61},"\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: adjuntos, Proofing, correo al proyecto, formularios o tareas automáticas desde un widget, comparados.",{"src":13,"card":14,"alt":60,"width":16,"height":17},"Capturas anotadas de una web convertidas en tareas de Asana","asana",{"path":63,"title":64,"description":65,"date":8,"modified":8,"locale":43,"category":11,"image":66,"translationKey":70},"\u002Fes\u002Fblog\u002Fchecklist-qa-web-antes-de-lanzar","Checklist web: más de 60 comprobaciones antes de lanzar","Checklist web con más de 60 comprobaciones por áreas: formularios, enlaces, móvil, navegadores, velocidad, SEO y accesibilidad, con plantilla Excel gratis.",{"src":67,"card":68,"alt":69,"width":16,"height":17},"\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",{"path":72,"title":73,"description":74,"date":8,"modified":8,"locale":43,"category":11,"image":75,"translationKey":77},"\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 y Word, con ejemplos de un informe de bugs bueno y uno malo, y los campos que importan en una web.",{"src":13,"card":14,"alt":76,"width":16,"height":17},"Código JavaScript en una pantalla, ilustrando cómo escribir un informe de bugs de una web","bug-report",{"path":79,"title":80,"description":81,"date":8,"modified":8,"locale":43,"category":11,"image":82,"translationKey":38},"\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 recoger feedback de clientes en una web: 5 métodos comparados, un proceso de revisión paso a paso y un email de ejemplo para explicárselo al cliente.",{"src":35,"card":36,"alt":83,"width":16,"height":17},"Diseñador web en su mesa revisando el feedback de clientes sobre una web",{"path":85,"title":86,"description":87,"date":8,"modified":8,"locale":43,"category":23,"image":88,"translationKey":90},"\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: propiedades de la base de datos, vistas tablero y rutina de triaje, y cómo recibir el feedback del cliente solo.",{"src":25,"card":26,"alt":89,"width":28,"height":16},"Equipo organizando bugs y feedback de clientes de una web en Notion","notion",{"path":92,"title":93,"description":94,"date":8,"modified":8,"locale":43,"category":95,"image":96,"translationKey":98},"\u002Fes\u002Fblog\u002Fherramientas-gratis-seguimiento-bugs","Herramientas gratis de seguimiento de bugs para webs (2026)","Herramientas gratis de seguimiento de bugs para equipos web: GitHub Issues, Jira, Trello, Linear, Notion, Asana y feedback visual, con límites comprobados.","comparisons",{"src":67,"card":68,"alt":97,"width":16,"height":17},"Equipo revisando incidencias en una herramienta gratis de seguimiento de bugs","free-bug-tracking",{"path":100,"title":101,"description":102,"date":8,"modified":9,"locale":43,"category":11,"image":103,"translationKey":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, checklist de 12 criterios, plantilla de puntuación y prueba de una semana.",{"src":13,"card":14,"alt":104,"width":16,"height":17},"Código en una pantalla, ilustración de cómo elegir entre herramientas de feedback visual web",{"path":106,"title":107,"description":108,"date":8,"modified":8,"locale":43,"category":11,"image":109,"translationKey":113},"\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, criterios de aceptación y una plantilla gratis en Excel.",{"src":110,"card":111,"alt":112,"width":16,"height":17},"\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",{"path":115,"title":116,"description":117,"date":8,"modified":8,"locale":43,"category":11,"image":118,"translationKey":120},"\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":35,"card":36,"alt":119,"width":16,"height":17},"Diseñador web revisando el feedback visual sobre una interfaz","visual-feedback",{"path":122,"title":123,"description":124,"date":125,"modified":8,"locale":10,"category":23,"image":126,"translationKey":90},"\u002Fblog\u002Fsupercharge-your-workflow-with-the-notion-bug-tracker-extension","Notion Bug Tracker Template (Free) for Website Projects","A free Notion bug tracker template for website projects: import the CSV, get the right properties and board views, and send client feedback into it.","2025-04-24T16:17:44+00:00",{"src":25,"card":26,"alt":127,"width":28,"height":16},"Team organizing website bugs and client feedback in a Notion bug tracker",{"path":129,"title":130,"description":131,"date":132,"modified":8,"locale":10,"category":11,"image":133,"translationKey":113},"\u002Fblog\u002Fuser-acceptance-testing-in-software-development","User Acceptance Testing (UAT): Template, Checklist & Examples","What user acceptance testing is, UAT vs QA, example test scenarios, exit criteria and a free UAT test plan and sign-off template (Excel) for websites.","2023-09-28T17:32:27+00:00",{"src":110,"card":111,"alt":134,"width":16,"height":17},"Client doing user acceptance testing on a new website at his desk",{"path":136,"title":137,"description":138,"date":139,"modified":8,"locale":10,"category":95,"image":140,"translationKey":98},"\u002Fblog\u002Fbug-tracking-tools-free","Free Bug Tracking Tools for Web Teams (2026 Guide)","Free bug tracking tools for web teams compared: GitHub Issues, Jira, Trello, Linear, Notion, Asana and visual feedback tools, with verified free-plan limits.","2023-09-21T16:56:47+00:00",{"src":67,"card":68,"alt":141,"width":16,"height":17},"Team at a computer reviewing issues in a free bug tracking tool",{"path":143,"title":144,"description":145,"date":146,"modified":8,"locale":10,"category":11,"image":147,"translationKey":77},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report","Bug Report Template (Free Excel & Word) + Examples","Free bug report template for Excel, Google Sheets and Word, with good and bad bug report examples and the fields that matter for website bugs.","2023-09-11T14:43:18+00:00",{"src":13,"card":14,"alt":148,"width":16,"height":17},"JavaScript code on a screen, illustrating how to write a bug report for a website",{"path":150,"title":151,"description":152,"date":153,"modified":8,"locale":10,"category":23,"image":154,"translationKey":61},"\u002Fblog\u002F1-way-to-get-annotated-screengrabs-into-asana","Asana Bug Tracking: Get Annotated Screenshots into Tasks","Get annotated screenshots and website feedback into Asana: attachments, Proofing, email-to-task, Forms or automatic tasks from a feedback widget, compared.","2023-09-11T11:56:04+00:00",{"src":13,"card":14,"alt":155,"width":16,"height":17},"Annotated screenshots of a website being turned into Asana tasks",{"path":157,"title":158,"description":159,"date":160,"modified":8,"locale":10,"category":11,"image":161,"translationKey":70},"\u002Fblog\u002Fspeed-up-qa-testing","Website QA Checklist: 60+ Checks Before Launch (Free Template)","A website QA checklist with 60+ checks grouped by area (forms, links, devices, browsers, speed, SEO, accessibility), plus a free Excel template to download.","2023-08-19T11:32:36+00:00",{"src":67,"card":68,"alt":162,"width":16,"height":17},"Person running a website QA checklist on a laptop before launch",{"path":164,"title":165,"description":166,"date":167,"modified":8,"locale":10,"category":11,"image":168,"translationKey":120},"\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, benefits, examples, tool checklist.","2023-08-09T17:41:00+00:00",{"src":35,"card":36,"alt":169,"width":16,"height":17},"Web designer reviewing visual feedback on a website interface",{"path":171,"title":172,"description":173,"date":174,"modified":8,"locale":10,"category":11,"image":175,"translationKey":48},"\u002Fblog\u002Fscreen-grab-annotation-apps","How to Annotate Website Screenshots (and Send Them to Devs)","How to annotate website screenshots with OS tools, browser features, dedicated apps or a feedback widget. Compare options and prices, with a good example.","2023-08-02T23:25:13+00:00",{"src":45,"card":46,"alt":176,"width":16,"height":17},"Person at a computer annotating website screenshots for a developer",{"id":178,"title":144,"body":179,"category":11,"date":146,"description":145,"extension":586,"faq":587,"image":600,"locale":10,"meta":601,"modified":8,"navigation":602,"path":143,"seo":603,"seoTitle":604,"stem":605,"tags":606,"tldr":611,"translationKey":77,"__hash__":612},"blog\u002Fblog\u002Fwhat-to-put-in-a-bug-report.md",{"type":180,"value":181,"toc":570},"minimark",[182,186,192,197,200,203,207,345,350,385,388,392,395,406,409,413,417,429,432,436,442,450,454,493,497,505,508,511,515,522,525,542,549,567],[183,184,185],"p",{},"Learning how to write a bug report is the cheapest way to get bugs fixed faster. A developer who receives \"the form doesn't work\" has to ask four follow-up questions before starting. One who receives a URL, a browser version, three steps and a marked-up screenshot can usually reproduce it within minutes. Below you'll find the fields that matter for websites, a free template you can copy, and a bad vs good example.",[187,188],"template-download",{"files":189,"text":190,"title":191},"Excel|\u002Ftemplates\u002Fbug-report-template.xlsx,Word|\u002Ftemplates\u002Fbug-report-template.docx,CSV|\u002Ftemplates\u002Fbug-report-template.csv","Excel (opens in Google Sheets), Word and CSV, with dropdowns and two filled-in examples.","Free bug report template",[193,194,196],"h2",{"id":195},"what-is-a-bug-report","What is a bug report?",[183,198,199],{},"A bug report is a written description of a software problem that gives a developer enough information to reproduce it, understand it and fix it. For websites, that means where the problem happens, on which device and browser, how to trigger it, and what should have happened instead.",[183,201,202],{},"A bug report is not a complaint and not a feature request. \"I'd like the menu to be green\" is a change request. \"The menu doesn't open on iPhone\" is a bug.",[193,204,206],{"id":205},"the-fields-that-matter-for-website-bugs","The fields that matter for website bugs",[208,209,210,226],"table",{},[211,212,213],"thead",{},[214,215,216,220,223],"tr",{},[217,218,219],"th",{},"Field",[217,221,222],{},"What to write",[217,224,225],{},"Example",[227,228,229,241,257,268,279,290,301,312,323,334],"tbody",{},[214,230,231,235,238],{},[232,233,234],"td",{},"Title",[232,236,237],{},"Where + what, in a few words",[232,239,240],{},"\"Contact form: Send button does nothing on mobile\"",[214,242,243,246,249],{},[232,244,245],{},"URL",[232,247,248],{},"The exact page address",[232,250,251],{},[252,253,254],"a",{"href":254,"rel":255},"https:\u002F\u002Fexample.com\u002Fcontact\u002F",[256],"nofollow",[214,258,259,262,265],{},[232,260,261],{},"Browser + version",[232,263,264],{},"Name and version number",[232,266,267],{},"Safari 17.5",[214,269,270,273,276],{},[232,271,272],{},"Operating system",[232,274,275],{},"Name and version",[232,277,278],{},"iOS 17.5",[214,280,281,284,287],{},[232,282,283],{},"Screen size \u002F device",[232,285,286],{},"Resolution or device model",[232,288,289],{},"iPhone 13, 390×844",[214,291,292,295,298],{},[232,293,294],{},"Steps to reproduce",[232,296,297],{},"Numbered, starting from loading the page",[232,299,300],{},"1. Open the URL 2. Fill in all fields 3. Tap Send",[214,302,303,306,309],{},[232,304,305],{},"Expected result",[232,307,308],{},"What should happen",[232,310,311],{},"Form is sent and a thank-you message appears",[214,313,314,317,320],{},[232,315,316],{},"Actual result",[232,318,319],{},"What happens instead",[232,321,322],{},"Nothing happens; the button stays active",[214,324,325,328,331],{},[232,326,327],{},"Screenshot or video",[232,329,330],{},"The problem, marked up",[232,332,333],{},"Arrow pointing at the button",[214,335,336,339,342],{},[232,337,338],{},"Severity \u002F priority",[232,340,341],{},"Impact and urgency",[232,343,344],{},"High: no leads can come in from mobile",[346,347,349],"h3",{"id":348},"why-each-one-matters","Why each one matters",[351,352,353,361,367,373,379],"ul",{},[354,355,356,360],"li",{},[357,358,359],"strong",{},"URL."," \"The services page\" can mean three different pages on a site with several languages or a staging and live version. Copy the address bar.",[354,362,363,366],{},[357,364,365],{},"Browser, OS and screen size."," Many website bugs only happen in one browser or at one width. Without this, the developer tests on their own setup, sees nothing wrong and closes the report as \"cannot reproduce\".",[354,368,369,372],{},[357,370,371],{},"Steps to reproduce."," A screenshot proves the bug exists; the steps show how to make it happen again. Start from a fresh page load and number each action.",[354,374,375,378],{},[357,376,377],{},"Expected vs. actual result."," This is what turns \"it doesn't work\" into something testable. Sometimes it also reveals that the site is behaving as designed and the request is really a change.",[354,380,381,384],{},[357,382,383],{},"Screenshot."," A marked-up screenshot removes ambiguity about which element you mean. Draw an arrow or a box on the exact spot.",[183,386,387],{},"Optional but useful: whether it happens every time or only sometimes, whether you're logged in, the browser language, and console errors if you're technical enough to open the developer tools.",[193,389,391],{"id":390},"free-bug-report-template-copy-and-paste","Free bug report template (copy and paste)",[183,393,394],{},"Paste this into an email, a doc, a GitHub issue, a Notion page or whatever tracker you use:",[396,397,403],"pre",{"className":398,"code":400,"language":401,"meta":402},[399],"language-text","Title: [Page\u002Ffeature]: [what goes wrong], [where\u002Fwhen]\n\nURL: \nBrowser + version: \nOperating system + version: \nDevice \u002F screen size: \nLogged in? (yes\u002Fno, which role): \n\nSteps to reproduce:\n1. \n2. \n3. \n\nExpected result:\n\n\nActual result:\n\n\nHappens: [every time \u002F sometimes \u002F once]\nSeverity: [critical \u002F high \u002F medium \u002F low]\nScreenshot or recording: [attach, with the problem marked]\nNotes: \n","text","",[404,405,400],"code",{"__ignoreMap":402},[183,407,408],{},"Keep one bug per report. If you find three problems on the same page, write three reports.",[193,410,412],{"id":411},"bad-vs-good-bug-report-example","Bad vs good bug report example",[346,414,416],{"id":415},"bad","Bad",[418,419,420,426],"blockquote",{},[183,421,422,425],{},[357,423,424],{},"Title:"," Form broken",[183,427,428],{},"The contact form isn't working, please fix ASAP!!",[183,430,431],{},"The developer doesn't know which form (the site has two), on what device, what \"not working\" means, or whether it's urgent compared to anything else.",[346,433,435],{"id":434},"good","Good",[396,437,440],{"className":438,"code":439,"language":401,"meta":402},[399],"Title: Contact form: Send button does nothing on iPhone (Safari)\n\nURL: https:\u002F\u002Fstaging.example.com\u002Fcontact\u002F\nBrowser + version: Safari 17.5\nOperating system + version: iOS 17.5\nDevice \u002F screen size: iPhone 13, 390x844\nLogged in? No\n\nSteps to reproduce:\n1. Open https:\u002F\u002Fstaging.example.com\u002Fcontact\u002F on the iPhone\n2. Fill in Name, Email and Message with valid data\n3. Tap \"Send\"\n\nExpected result:\nThe form is submitted and the message \"Thanks, we'll be in touch\" appears.\n\nActual result:\nNothing happens. No message, no error, the fields keep their content.\nOn desktop Chrome 129 (Windows 11) the same steps work.\n\nHappens: every time (tried 3 times)\nSeverity: high (mobile visitors can't contact the client)\nScreenshot: attached, Send button circled in red\n",[404,441,439],{"__ignoreMap":402},[183,443,444,445,449],{},"The good report takes about two minutes longer to write and can save a lot more than that in back-and-forth. Notice the extra line about desktop Chrome: saying where the bug does ",[446,447,448],"em",{},"not"," happen is one of the most useful clues you can give.",[193,451,453],{"id":452},"tips-for-writing-better-bug-reports","Tips for writing better bug reports",[455,456,457,463,469,475,481,487],"ol",{},[354,458,459,462],{},[357,460,461],{},"Reproduce it once before reporting."," If you can't make it happen again, say so (\"happened once, couldn't reproduce\").",[354,464,465,468],{},[357,466,467],{},"Write the title last."," Once you've written the steps, the title is easier to make specific.",[354,470,471,474],{},[357,472,473],{},"Describe, don't diagnose."," \"The image is blurry on the homepage hero\" is better than \"the image compression is wrong\". Leave the cause to the developer.",[354,476,477,480],{},[357,478,479],{},"Use neutral language."," Capital letters and exclamation marks don't speed up a fix.",[354,482,483,486],{},[357,484,485],{},"Check for duplicates."," Search the tracker before adding a new report.",[354,488,489,492],{},[357,490,491],{},"Add what you already tried."," Another browser, clearing the cache, a different device: each one narrows down the cause.",[193,494,496],{"id":495},"why-clients-and-testers-skip-half-the-fields","Why clients and testers skip half the fields",[183,498,499,500,504],{},"Even with a template, non-technical people rarely know their browser version or screen resolution, and copying URLs and taking marked-up screenshots by hand takes time. That's when you get \"form broken\" reports, especially from clients reviewing a site during a ",[252,501,503],{"href":502},"\u002Fblog\u002Fhow-to-collect-client-feedback-on-a-website\u002F","client feedback round",".",[183,506,507],{},"The fix is to capture the technical fields automatically so the reporter only writes what a human has to write: the steps, the expected result and the actual result.",[509,510],"blog-cta",{},[193,512,514],{"id":513},"how-givefeedbackio-fills-in-the-template-for-you","How GiveFeedback.io fills in the template for you",[183,516,517,521],{},[252,518,520],{"href":519},"\u002F","GiveFeedback.io"," adds a \"Give Feedback\" button to your website with one JavaScript snippet. When someone clicks it (no account needed), the browser asks permission to capture the tab, and they can mark up a screenshot of the visible page with arrows, boxes, text, a pen or a highlighter. They then add a title, a description and a type such as Bug.",[183,523,524],{},"These fields from the template are attached automatically to every report:",[351,526,527,530,533,536,539],{},[354,528,529],{},"Page URL",[354,531,532],{},"Browser and version",[354,534,535],{},"Operating system and version",[354,537,538],{},"Screen resolution and whether it's a mobile device",[354,540,541],{},"Browser language and timezone",[183,543,544],{},[545,546],"img",{"alt":547,"src":548},"A feedback report in GiveFeedback.io showing the screenshot and the browser data captured automatically","\u002Fwp-content\u002Fuploads\u002F2024\u002F01\u002Fbrowser-1920-1080-1-task-info.jpg",[183,550,551,552,556,557,561,562,566],{},"What it doesn't capture: console logs, network requests or video, and it captures the visible viewport rather than the full page. For bugs that need logs or a recording, a developer will still have to dig in. Reports land in a dashboard where you mark them Open, Resolved or Archived, and can be sent automatically to ",[252,553,555],{"href":554},"\u002Fnotion-bug-tracking-tool\u002F","Notion"," or ",[252,558,560],{"href":559},"\u002Fasana-bug-tracking-tool\u002F","Asana",". The Free plan covers 5 projects and 50 feedback reports; see ",[252,563,565],{"href":564},"\u002Fpricing\u002F","pricing"," for the rest.",[183,568,569],{},"Whether you use a tool or a plain template, the rule is the same: one bug per report, the exact URL and setup, numbered steps, and expected versus actual result. Get those right and most bugs are fixed on the first try.",{"title":402,"searchDepth":571,"depth":571,"links":572},2,[573,574,578,579,583,584,585],{"id":195,"depth":571,"text":196},{"id":205,"depth":571,"text":206,"children":575},[576],{"id":348,"depth":577,"text":349},3,{"id":390,"depth":571,"text":391},{"id":411,"depth":571,"text":412,"children":580},[581,582],{"id":415,"depth":577,"text":416},{"id":434,"depth":577,"text":435},{"id":452,"depth":571,"text":453},{"id":495,"depth":571,"text":496},{"id":513,"depth":571,"text":514},"md",[588,591,594,597],{"question":589,"answer":590},"What should a bug report include?","A specific title, the page URL, the environment (browser, OS, screen size), numbered steps to reproduce, the expected result, the actual result and a screenshot or recording. Severity and priority help the team decide what to fix first.",{"question":592,"answer":593},"What is the difference between expected and actual result in a bug report?","The expected result is what should happen if the site worked correctly; the actual result is what happens instead. Writing both removes guesswork, because some 'bugs' turn out to be features working as designed.",{"question":595,"answer":596},"How do I write a good bug report title?","Name the place and the problem in under about ten words, for example 'Checkout: Pay button does nothing on Safari iOS'. Avoid vague titles like 'Bug' or 'Site broken'.",{"question":598,"answer":599},"Should I report several bugs in one report?","No. Write one report per bug. Separate reports can be assigned, fixed and closed independently, and nothing gets lost when one part is fixed and another isn't.",{"src":13,"card":14,"alt":148,"width":16,"height":17},{},true,{"title":144,"description":145},"Bug Report Template: Free Excel, Word & Example","blog\u002Fwhat-to-put-in-a-bug-report",[607,608,609,610],"bug report","template","QA","website testing","A good bug report tells a developer where the bug happens (URL), on what setup (browser, OS, screen size), how to reproduce it (numbered steps), what should happen versus what actually happens, and shows it with a marked-up screenshot. One bug per report, with a short, specific title.","EPqy1ZAjC3m4JFjlu2nmFCuY7sMhvDL5J-BxMylzR6E",1792593618678]