PageSourceSearch

https://findbugs.app/changelog.html

html findbugs.app collected 2026-10-02 01:13:23 UTC 35,861 bytes, 486 lines download raw bytes

1<!DOCTYPE html>
2<html lang="en">
3<head>
4  <meta charset="UTF-8">
5  <meta name="viewport" content="width=device-width, initial-scale=1">
6  <title>What's New — Bug Reporter changelog</title>
7  <meta name="description" content="Release notes and feature updates for Bug Reporter — the free bug-reporting browser extension and team dashboard. See what shipped in each version.">
8  <link rel="canonical" href="https://findbugs.app/changelog.html">
9  <meta name="theme-color" content="#c2603f">
10  <link rel="icon" type="image/png" href="/favicon.png">
11  <meta property="og:type" content="website">
12  <meta property="og:site_name" content="Bug Reporter">
13  <meta property="og:title" content="What's New — Bug Reporter changelog">
14  <meta property="og:description" content="Release notes and feature updates for Bug Reporter. See what shipped in each version.">
15  <meta property="og:url" content="https://findbugs.app/changelog.html">
16  <style>
17    :root {
18      /* "Claude look": clay/coral accent + warm ivory neutrals (matches the app) */
19      --blue: #c2603f; --blue-dark: #a8482c; --blue-50: #f9efe9; --blue-100: #f2ded2;
20      --ink: #29241f; --muted: #6f665e; --line: #e6ded2; --bg: #fffdf9; --band: #f3efe8;
21      --serif: "Fraunces", "Iowan Old Style", Georgia, "Times New Roman", serif;
22    }
23    @font-face {
24      font-family: "Fraunces";
25      src: url("/fonts/fraunces.woff2") format("woff2");
26      font-weight: 100 900; font-display: swap;
27    }
28    * { box-sizing: border-box; margin: 0; padding: 0; }
29    body { font-family: "Inter", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
30      color: var(--ink); background: var(--bg); line-height: 1.6; -webkit-font-smoothing: antialiased; }
31    a { color: var(--blue-dark); text-decoration: none; }
32    a:hover { text-decoration: underline; }
33    /* inline links inside body copy stay underlined (distinguishable without colour) */
34    main p a, .release a { text-decoration: underline; }
35    .wrap { max-width: 800px; margin: 0 auto; padding: 0 24px; }
36    h1, h2, h3 { font-family: var(--serif); font-weight: 600; line-height: 1.2; letter-spacing: -0.015em; }
37
38    .topbar { position: sticky; top: 0; z-index: 50; background: rgba(255,255,255,.9);
39      backdrop-filter: blur(10px); border-bottom: 1px solid var(--line); }
40    .topbar .wrap { max-width: 1080px; display: flex; align-items: center; gap: 20px; height: 62px; }
41    .brand { font-weight: 800; font-size: 18px; color: var(--ink); }
42    .navlinks { display: flex; flex-wrap: wrap; gap: 12px 20px; margin-left: auto; align-items: center; justify-content: flex-end; }
43    .navlinks a { color: var(--muted); font-weight: 500; font-size: 14px; }
44    .navlinks a:hover { color: var(--ink); text-decoration: none; }
45    .btn { display: inline-block; border-radius: 9px; padding: 9px 16px; font-weight: 700; font-size: 14px;
46      background: var(--blue-dark); color: #fff; }
47    .btn:hover { background: #8a3a22; text-decoration: none; }
48    /* keep the nav "Sign up free" button white/bold (.navlinks a is more specific) */
49    .navlinks a.btn, .navlinks a.btn:hover { color: #fff; font-weight: 700; }
50
51    .head { text-align: center; padding: 60px 0 24px;
52      background: radial-gradient(900px 380px at 50% -80px, var(--blue-50), transparent); }
53    .head h1 { font-size: 40px; font-weight: 850; }
54    .head p { color: var(--muted); font-size: 18px; margin-top: 12px; }
55
56    main { padding: 24px 0 60px; }
57    .release { border-left: 2px solid var(--line); padding: 0 0 8px 24px; margin-left: 6px; position: relative; }
58    .release::before { content: ""; position: absolute; left: -7px; top: 6px; width: 12px; height: 12px;
59      border-radius: 50%; background: var(--blue); box-shadow: 0 0 0 4px var(--blue-50); }
60    .release .meta { display: flex; align-items: baseline; gap: 12px; flex-wrap: wrap; margin-top: 22px; }
61    .release .ver { font-weight: 800; font-size: 20px; }
62    .release .date { color: var(--muted); font-size: 14px; }
63    .tag { display: inline-block; font-size: 11px; font-weight: 700; text-transform: uppercase; letter-spacing: .04em;
64      padding: 2px 8px; border-radius: 999px; background: var(--blue-50); color: var(--blue-dark); }
65    .release h3 { font-size: 15px; margin: 16px 0 6px; }
66    .release ul { margin: 0 0 4px 20px; }
67    .release li { margin: 5px 0; color: #1f2937; }
68    .release li b { color: var(--ink); }
69    footer { border-top: 1px solid var(--line); padding: 30px 0; color: var(--muted); font-size: 14px; }
70    footer .wrap { max-width: 1080px; display: flex; justify-content: space-between; flex-wrap: wrap; gap: 12px; }
71    footer a { color: var(--muted); }
72  </style>
73</head>
74<body>
75  <header class="topbar">
76    <div class="wrap">
77      <a class="brand" href="/" style="color:var(--ink)">🐞 Bug Reporter</a>
78      <nav class="navlinks">
79        <a href="/">Home</a>
80        <a href="/help.html">Help</a>
81        <a href="/login.html">Log in</a>
82        <a class="btn" href="/signup.html">Sign up free</a>
83      </nav>
84    </div>
85  </header>
86
87  <div class="head">
88    <div class="wrap">
89      <h1>
89What's New</h1>
90      <p>Every meaningful update to Bug Reporter, newest first.</p>
91    </div>
92  </div>
93
94  <main>
95    <div class="wrap">
96
97      <div class="release">
98        <div class="meta"><span class="ver">v1.6.8</span><span class="date">3 August 2026</span><span class="tag">Fix</span></div>
99        <h3>📸 Recording fixes + choose how the plugin opens</h3>
100        <ul>
101          <li><b>Step screenshots fixed on Chrome 150.</b> The newest Chrome quietly stopped honoring the screenshot access the plugin had — steps recorded fine but arrived with no images. The plugin now checks the real capture capability at <b>Start recording</b> and asks for the one permission Chrome accepts (a one-time prompt; approve it and screenshots are back for good).</li>
102          <li><b>No more silent blanks.</b> If screenshot access is missing you choose <b>Allow screenshots</b> or <b>Record without screenshots</b>; the status and finish summary say which mode you're in, and dashboard steps without an image now explain why instead of showing nothing.</li>
103          <li><b>Device-kept videos play again.</b> Privacy-mode videos could freeze the card at "Loading from your device…" — a video-format quirk in the player, now fixed, with a folder/file fallback if anything else ever goes wrong.</li>
104          <li><b>Choose how the plugin opens.</b> New <b>"Opens as"</b> switch in the plugin header: docked side panel (default) or the classic popup.</li>
105          <li>Extension <b>v1.6.8</b>.</li>
106        </ul>
107      </div>
108
109      <div class="release">
110        <div class="meta"><span class="ver">v1.6.7</span><span class="date">3 August 2026</span><span class="tag">Feature</span></div>
111        <h3>🔒 Privacy &amp; account-security release</h3>
112        <ul>
113          <li><b>Typed-value capture is now OFF by default.</b> While recording a bug, the extension records <i>which</i> fields you interacted with — but no longer the text you typed — unless a workspace admin explicitly turns value capture on (Settings → Privacy). Passwords were always excluded; now everything you type is.</li>
114          <li><b>See and sign out your devices.</b> Your Account page lists every active session (browser, last used) and lets you sign out any one of them — or everywhere at once. Changing your password now signs out other sessions too.</li>
115          <li><b>Workspace media privacy mode.</b> Admins can keep screenshots and recordings off our servers entirely: media goes to your connected Google Drive/OneDrive, or stays on the reporter's device.</li>
116          <li><b>Clearer sign-in problems.</b> Login and password-reset errors now say what actually went wrong (coded, so support can trace them) instead of a generic failure.</li>
117          <li><b>Faster on big workspaces.</b> Videos now stream (seek without downloading the whole file) and long bug lists load in pages.</li>
118          <li>Plus a large invisible batch: backup tooling, a durable email queue, stricter security headers, and a major internal restructure — behaviour-identical, verified by the full 693-test suite. Extension <b>v1.6.7</b>.</li>
119        </ul>
120      </div>
121
122      <div class="release">
123        <div class="meta"><span class="ver">Jira</span><span class="date">31 July 2026</span><span class="tag">Feature</span></div>
124        <h3>🔗 Guided Jira setup</h3>
125        <ul>
126          <li>Settings → Jira now has a <b>📖 Step-by-step guide</b> popup that walks you through the whole setup: Jira address, API token, account email, project key, <b>Test connection</b> + <b>Verify project</b>, creating a ticket from a bug, and the optional <b>2-way status sync</b> webhook (with the status mapping).</li>
127          <li>Each step has a screenshot to follow along.</li>
128        </ul>
129      </div>
130
131      <div class="release">
132        <div class="meta"><span class="ver">Replay</span><span class="date">31 July 2026</span><span class="tag">Fix</span></div>
133        <h3>🔁 Smarter in-browser replay on complex apps</h3>
134        <ul>
135          <li>"Run test now" now picks the <b>visible</b> element when a label (e.g. "Add New") appears more than once — a hidden duplicate in an inactive tab/panel no longer causes a false "element not found." It still won't guess when two are genuinely visible.</li>
136          <li>After a view-changing click it <b>waits for the page to settle</b> so async content renders before the next step.</li>
137          <li>Extension <b>v1.6.6</b>.</li>
138        </ul>
139      </div>
140
141      <div class="release">
142        <div class="meta"><span class="ver">Simpler UI</span><span class="date">29 July 2026</span><span class="tag">Change</span></div>
143        <h3>🧹 Long screenshot removed from the plugin</h3>
144        <ul>
145          <li>Removed the <b>Long screenshot</b> (full-page stitch) action — the popup is now <b>Record bug</b>, <b>Record feature (with audio)</b>, <b>Screenshot</b>, and <b>Start agent recording</b>.</li>
146          <li>Extension <b>v1.6.5</b>.</li>
147        </ul>
148      </div>
149
150      <div class="release">
151        <div class="meta"><span class="ver">Videos</span><span class="date">29 July 2026</span><span class="tag">Feature</span></div>
152        <h3>
152📼 Feature videos now appear in the Videos library (from your device)</h3>
153        <ul>
154          <li>A feature video (🎥 Record feature → Submit as user flow) recorded while your workspace keeps media off our servers now shows as a card in the <b>Videos library</b>, badged <b>"🔒 On your device"</b>, and <b>plays there</b> — loaded back from your computer via the extension. The bytes are never uploaded (only its title/length are registered).</li>
155          <li>If the in-browser copy isn't handy, <b>connect your <code>Downloads/FindBugs</code> folder once</b> and local videos play automatically (or pick the file) — like local bug screenshots.</li>
156          <li>It plays on the computer that recorded it; connect Google Drive or OneDrive to share feature videos with the whole team.</li>
157          <li>Extension <b>v1.6.3</b>.</li>
158        </ul>
159      </div>
160
161      <div class="release">
162        <div class="meta"><span class="ver">Videos</span><span class="date">29 July 2026</span><span class="tag">Feature</span></div>
163        <h3>🎬 Videos that just work in privacy mode</h3>
164        <ul>
165          <li><b>Feature videos</b> no longer dead-end with an error when your workspace keeps media off our servers — the recording is <b>saved to your <code>Downloads/FindBugs</code> folder</b>, with a one-time note that connecting Google Drive or OneDrive would add them to the shared library instead.</li>
166          <li><b>Bug videos are clearer:</b> after recording, the extension shows <b>"🎬 Video attached"</b> so you can see it'll go on the next bug you Submit — and it plays on the bug's page, loaded from your device.</li>
167          <li><b>Desktop agent recordings now show on the web</b> — the agent bug page loads the recording straight from your <code>FindBugs</code> folder and plays it. Nothing leaves your device.</li>
168          <li>Extension <b>v1.6.1</b>, desktop agent <b>v0.1.5</b>.</li>
169        </ul>
170      </div>
171
172      <div class="release">
173        <div class="meta"><span class="ver">Annotate</span><span class="date">29 July 2026</span><span class="tag">Feature</span></div>
174        <h3>✏️ Annotate screenshots &amp; edit bugs on the dashboard</h3>
175        <ul>
176          <li>New <b>Annotate</b> on a bug's screenshots (step lightbox + page screenshot): draw <b>boxes, arrows, text labels, and redaction boxes</b>.</li>
177          <li>Non-destructive overlays saved as lightweight coordinates — works even when media is kept off our servers (privacy mode); nothing extra is uploaded.</li>
178          <li>You can now <b>edit a bug's description &amp; title</b> on the bug page (reporter or QA/admin).</li>
179        </ul>
180      </div>
181
182      <div class="release">
183        <div class="meta"><span class="ver">Simpler UI</span><span class="date">29 July 2026</span><span class="tag">Feature</span></div>
184        <h3>✨ A much simpler extension — five clear actions</h3>
185        <ul>
186          <li>The popup is now a clean launcher: <b>Record bug</b>, <b>Record feature (with audio)</b>, <b>Screenshot</b>, <b>Long screenshot</b>, <b>Start agent recording</b>.</li>
187          <li>One small "What went wrong?" box for bugs (type/severity default, set on the dashboard); "Record feature" publishes a narrated video to your Videos library.</li>
188          <li>Removed the clutter (preview, templates, dropdowns, tester tools, link checker, dashcam, in-page editing, download-report). Screenshot annotation is moving to the dashboard next.</li>
189        </ul>
190      </div>
191
192      <div class="release">
193        <div class="meta"><span class="ver">Export</span><span class="date">29 July 2026</span><span class="tag">Feature</span></div>
194        <h3>📦 Export all your media to one .zip</h3>
195        <ul>
196          <li>New <b>Settings → Export all media</b> (admin): one <code>.zip</code> with every bug's screenshots &amp; video — from our servers <b>and</b> your connected Drive/OneDrive — organized per bug, with an index.</li>
197          <li>Great for a local backup or moving off cloud in one click. Media kept only on a reporter's device (privacy mode) isn't included.</li>
198        </ul>
199      </div>
200
201      <div class="release">
202        <div class="meta"><span class="ver">Recording</span><span class="date">28 July 2026</span><span class="tag">Fix</span></div>
203        <h3>🎥 Recording no longer stops when the page changes</h3>
204        <ul>
205          <li>Recording used to end the moment a page did a full reload or navigation (form submit, "next" button, login redirect) — cutting out on form-heavy flows.</li>
206          <li>Now recording <b>continues across page changes on the same website</b> — the recorder re-arms on each new page and keeps capturing your steps.</li>
207          <li>Flows that jump to a <b>different</b> website still end there for now (cross-site recording is coming next).</li>
208        </ul>
209      </div>
210
211      <div class="release">
212        <div class="meta"><span class="ver">Privacy fix</span><span class="date">28 July 2026</span><span class="tag">Fix</span></div>
213        <h3>🔒 Agent recordings now honor "keep media off our servers"</h3>
214        <ul>
215          <li>The desktop-agent path was uploading its session video (and trace) to our server even when Media privacy was ON.</li>
216          <li>Now, with privacy on, those artifacts are refused server-side and kept on the reporter's device — matching the extension's own recordings.</li>
217        </ul>
218      </div>
219
220      <div class="release">
221        <div class="meta"><span class="ver">Screenshot fix</span><span class="date">28 July 2026</span><span class="tag">Fix</span></div>
222        <h3>📸 Fixed: screenshots were silently failing to capture</h3>
223        <ul>
224          <li>In the side-panel view Chrome only grants screenshot access momentarily on toolbar-click, so if the panel was already open (or you'd switched tabs) captures silently failed and steps had blank screenshots.</li>
225          <li>Now "Start recording" asks once for durable capture permission, so screenshots work throughout the recording.</li>
226          <li>If a page still can't be captured you get a clear "Allow screenshots" button instead of a silent blank.</li>
227        </ul>
228      </div>
229
230      <div class="release">
231        <div class="meta"><span class="ver">Video fix</span><span class="date">28 July 2026</span><span class="tag">Fix</span></div>
232        <h3>🎬 A recorded video no longer shows up on the wrong bug</h3>
233        <ul>
234          <li>The extension wasn't clearing a recorded video after submit, so a leftover clip could attach to a later bug (and even appear on its dashboard page) even if that bug had no video.</li>
235          <li>Now each bug carries only the video attached when you pressed Submit, and the clip is cleared right after — no leaks into the next bug.</li>
236        </ul>
237      </div>
238
239      <div class="release">
240        <div class="meta"><span class="ver">Save folder</span><span class="date">28 July 2026</span><span class="tag">Feature</span></div>
241        <h3>📁 Bug files now save to one fixed folder (Downloads/FindBugs)</h3>
242        <ul>
243          <li>Every bug's <code>.zip</code> saves into <b>Downloads/FindBugs/</b> automatically — one predictable place, so connecting the folder on the dashboard always picks the right one.</li>
244          <li>Rename it any time in the extension's <b>Options</b>.</li>
245          <li>If Chrome asks where to save each file you'll confirm once per bug (pre-set to FindBugs); turn that Chrome setting off for zero prompts.</li>
246        </ul>
247      </div>
248
249      <div class="release">
250        <div class="meta"><span class="ver">Seamless local</span><span class="date">28 July 2026</span><span class="tag">Feature</span></div>
251        <h3>✨ Local media just appears on the dashboard — no picking</h3>
252        <ul>
253          <li>Open a bug whose media was kept on your device and the dashboard asks the extension for it and <b>renders the screenshots + video automatically</b> — no "choose a file", no prompt. Like cloud, but the media never leaves your computer (page ↔ extension only, never our servers).</li>
254          <li>Works on the computer where you recorded the bug. For the same seamless view <b>across devices</b>, connect your own Google Drive / OneDrive — same privacy, everywhere.</li>
255          <li>"Show media from my device" (open the .zip) and "Connect my FindBugs folder" remain as fallbacks.</li>
256        </ul>
257      </div>
258
259      <div class="release">
260        <div class="meta"><span class="ver">Local archive</span><span class="date">28 July 2026</span><span class="tag">Feature</span></div>
261        <h3>🗂️ A local copy of every bug's media — one file, one click</h3>
262        <ul>
263          <li><b>One .zip per bug:</b> the extension saves each bug's media as <code>Downloads/findbugs-&lt;BUG-NUMBER&gt;.zip</code> — the page screenshot (<code>page.png</code>), every step's screenshot (<code>step-01.png</code>…), the <code>video.webm</code> (when recorded), and a <code>report.html</code>. One file = one save, not a popup per screenshot.</li>
264          <li><b>Every bug:</b> you always have the full screenshots &amp; video on your computer, even when media is kept off our servers.</li>
265          <li><b>View in the app:</b> "Show media from my device" reads that <code>.zip</code> in your browser and renders it — nothing uploaded. Or "Connect my FindBugs folder" once (Chrome/Edge) and bugs load automatically.</li>
266        </ul>
267      </div>
268
269      <div class="release">
270        <div class="meta"><span class="ver">Privacy mode</span><span class="date">28 July 2026</span><span class="tag">Feature</span></div>
271        <h3>🔒 Keep media on your device — and still view it on the dashboard</h3>
272        <ul>
273          <li><b>Files you can find:</b>
273 with Media privacy on and no cloud connected, a bug's screenshots &amp; video are saved to your <b>Downloads</b> as one clearly-named file — <code>findbugs-&lt;BUG-NUMBER&gt;.html</code> (plus a playable <code>.webm</code> when you recorded a video). Open it directly to see everything.</li>
274          <li><b>View it in the app:</b> the bug page now has <b>"Show media from my device"</b> — pick that <code>findbugs-…</code> file and the dashboard renders the screenshots &amp; video right in the bug. The file is read on your computer and <b>never uploaded to our servers</b>.</li>
275          <li><b>Fixed:</b> in the side-panel view, a recorded video now shows as "🎬 Video attached" the moment you attach it.</li>
276        </ul>
277      </div>
278
279      <div class="release">
280        <div class="meta"><span class="ver">Your storage</span><span class="date">27 July 2026</span><span class="tag">Feature</span></div>
281        <h3>☁️ Bring-your-own storage &amp; safer sharing</h3>
282        <ul>
283          <li><b>Your cloud, your data:</b> connect Google Drive or OneDrive and a bug's screenshots &amp; videos live in <em>your</em> cloud, not on our servers — we only relay them to your team, never exposing the Drive/OneDrive link.</li>
284          <li><b>Privacy switch:</b> Settings → Media privacy → "Never store media on our servers." With it on and no cloud connected, media stays on the reporter's own device.</li>
285          <li><b>Workspace-only share links:</b> share a bug so only your logged-in workspace members can open it, with an optional expiry and one-click revoke. Public "anyone with the link" mode is still available.</li>
286        </ul>
287      </div>
288
289      <div class="release">
290        <div class="meta"><span class="ver">Remarks</span><span class="date">27 July 2026</span><span class="tag">Feature</span></div>
291        <h3>📝 Add internal notes to a bug — visible at a glance on the dashboard</h3>
292        <ul>
293          <li>Each bug now has a <b>Remarks</b> box — a shared place for your team to jot notes (latest text always shown). Admins &amp; QA can edit; reporters can read.</li>
294          <li>A <b>short preview</b> shows right in the bug list, so you can scan notes without opening each bug. Remarks are internal — never shown on public share links.</li>
295        </ul>
296      </div>
297
298      <div class="release">
299        <div class="meta"><span class="ver">Run test now</span><span class="date">27 July 2026</span><span class="tag">Feature</span></div>
300        <h3>▶️ Replay a recorded bug and get an instant pass/fail</h3>
301        <ul>
302          <li>Every bug now has a <b>Run test now</b> button — it re-plays the recorded steps in a tab in your own browser and tells you whether the bug still happens. Nothing runs on our servers.</li>
303          <li><b>Data sets &amp; expected results:</b> turn a recording into a repeatable test — supply different inputs and the answer you expect, and each run shows an expected-vs-actual check (catches wrong calculations, not just crashes).</li>
304          <li>First use asks a one-time "Enable in-browser test runs" permission. Requires the latest extension from the Chrome Web Store.</li>
305        </ul>
306      </div>
307
308      <div class="release">
309        <div class="meta"><span class="ver">Gallery</span><span class="date">27 July 2026</span><span class="tag">Feature</span></div>
310        <h3>🖼️ Screenshots open in a popup gallery instead of one long scroll</h3>
311        <ul>
312          <li>On a bug's "Steps to reproduce", each screenshot is now a small <b>thumbnail</b> — a bug with many steps no longer scrolls on forever.</li>
313          <li>Click any thumbnail to open a <b>full-size popup gallery</b>: flip through all screenshots with the arrows or your ← / → keys; press Esc or click outside to close. Works on shared bug links too.</li>
314        </ul>
315      </div>
316
317      <div class="release">
318        <div class="meta"><span class="ver">Replay</span><span class="date">27 July 2026</span><span class="tag">Fix</span></div>
319        <h3>✅ Replays no longer report a false "bug still reproduces"</h3>
320        <ul>
321          <li>
321When you re-ran a recorded flow, a test could be marked <b>failed</b> even though every step completed and nothing was actually broken — it was mistaking a normal, successful request for the original bug.</li>
322          <li>Now a request only counts as "the bug came back" if it <b>actually failed</b>. A clean replay of a working flow correctly shows a <b>pass</b>, while genuine errors are still caught.</li>
323        </ul>
324      </div>
325
326      <div class="release">
327        <div class="meta"><span class="ver">Layout</span><span class="date">27 July 2026</span><span class="tag">Fix</span></div>
328        <h3>📐 No more sideways scrolling on the bug page</h3>
329        <ul>
330          <li>A bug whose description or AI summary contained a very long link or code snippet could push the bug detail page sideways. Long links and text now <b>wrap</b>, so the page always fits its width.</li>
331          <li>Also folds in earlier responsive polish — the two-column bug page, wide tables, and the top navigation all resize cleanly on smaller laptops and tablets.</li>
332        </ul>
333      </div>
334
335      <div class="release">
336        <div class="meta"><span class="ver">Install</span><span class="date">20 July 2026</span><span class="tag">Feature</span></div>
337        <h3>🧩 One-click install — now on the Chrome Web Store</h3>
338        <ul>
339          <li>Install Bug Reporter in <b>one click</b> — the "Get the extension" page now has an <b>Add to Chrome</b> button, and it updates itself automatically.</li>
340          <li>No more manual download-and-unzip steps.</li>
341        </ul>
342      </div>
343
344      <div class="release">
345        <div class="meta"><span class="ver">New look</span><span class="date">20 July 2026</span><span class="tag">Feature</span></div>
346        <h3>🎨 A fresh new look</h3>
347        <ul>
348          <li><b>New design</b> across the whole app and website — a warm ivory canvas, a clay/coral accent, elegant serif headings, and softer cards. Same features and layout, a more refined feel.</li>
349          <li>Consistent from the marketing pages through login into the dashboard.</li>
350          <li><b>All-new videos</b> — every walkthrough re-recorded in the new look with calmer narration, plus two quick <b>15-second teasers</b>. The homepage now opens with a teaser of a bug being captured.</li>
351        </ul>
352      </div>
353
354      <div class="release">
355        <div class="meta"><span class="ver">Access</span><span class="date">20 July 2026</span><span class="tag">Fix</span></div>
356        <h3>♿ Accessibility &amp; polish</h3>
357        <ul>
358          <li><b>Better contrast</b> — links and labels are darker and comfortably readable (meets accessibility standards).</li>
359          <li><b>Screen-reader friendly</b> — every dropdown, form field, and page now has a proper name/heading, and keyboard users can reach wide tables.</li>
360          <li><b>Homepage fix</b> — the "How it works" and "Features" sections now always show (they could appear blank in some cases).</li>
361        </ul>
362      </div>
363
364      <div class="release">
365        <div class="meta"><span class="ver">Polish</span><span class="date">19 July 2026</span><span class="tag">Fix</span></div>
366        <h3>✨ Layout polish — no more cut-off text</h3>
367        <ul>
368          <li><b>Extension:</b> the Type, Category and Severity dropdowns now sit one per line and show their full text — no more clipping (e.g. "UI / Layout pro…") behind the arrow.</li>
369          <li><b>Dashboard:</b> removed a stray sideways scrollbar that could appear on some pages.</li>
370          <li><b>Dashboard:</b> refreshed the interface onto a modern, consistent component set — same familiar look, with tidier dropdowns and tooltips throughout.</li>
371        </ul>
372      </div>
373
374      <div class="release">
375        <div class="meta"><span class="ver">Videos</span><span class="date">17 July 2026</span><span class="tag">Feature</span></div>
376        <h3>🎬 Guided videos + a refreshed homepage</h3>
377        <ul>
378          <li>A narrated <b>50-second overview</b> now plays right on the homepage, with a "See it in action" strip of short walkthroughs.</li>
379          <li><b>Seven guided videos</b> in Help — each with an AI voice-over and captions: overview, report a bug, triage &amp; Jira, self-healing tests, the video library, analytics &amp;
379 the board, and admin setup.</li>
380          <li>Videos now ship as mp4 too, so they play everywhere (Safari/iOS included).</li>
381        </ul>
382      </div>
383
384      <div class="release">
385        <div class="meta"><span class="ver">Big update</span><span class="date">13 July 2026</span><span class="tag">Feature</span></div>
386        <h3>📋 Richer reports & in-page pins</h3>
387        <ul>
388          <li><b>Deeper technical capture</b> — reports now show the page's detected tech stack and its security headers, and every captured request can be copied as a <b>cURL</b> command or exported as a <b>Postman</b> collection.</li>
389          <li><b>Pin feedback to an element</b> — with the website widget, visitors can click any element on the page and attach a comment right there; the pins show up on the bug.</li>
390          <li><b>Tester tools in the extension</b> — a broken-link checker, ready-to-use report templates, a test-data generator, and a security-payload cheat-sheet.</li>
391          <li><b>Smarter triage emails</b> — assignees are emailed when a bug lands on them, reporters when their bug's status changes, plus an optional daily digest.</li>
392          <li><b>Attach a video later</b> — if a recording overflowed your free storage and was saved to your device, the bug now shows an "Attach the saved recording" prompt to upload it once storage is available.</li>
393        </ul>
394      </div>
395
396      <div class="release">
397        <div class="meta"><span class="ver">Email</span><span class="date">12 July 2026</span><span class="tag">Feature</span></div>
398        <h3>✉️ Email notifications are live</h3>
399        <ul>
400          <li>Forgot your password? You now get a secure, one-time reset link by email.</li>
401          <li>New members get a welcome email, and workspace admins can be emailed when a new bug is reported (toggle under <b>Account → Email preferences</b>).</li>
402          <li>Optional product-update newsletters, with one-click unsubscribe.</li>
403        </ul>
404      </div>
405
406      <div class="release">
407        <div class="meta"><span class="ver">Privacy</span><span class="date">12 July 2026</span><span class="tag">Privacy</span></div>
408        <h3>📝 Clearer signup &amp; email preferences</h3>
409        <ul>
410          <li>You now agree to the <a href="/terms.html">Terms of Service</a> and <a href="/privacy.html">Privacy Policy</a> when you sign up, and choose (opt-in) whether to receive product-update emails.</li>
411          <li>Manage all email preferences any time under <b>Account → Email preferences</b>, with one-click unsubscribe on every newsletter.</li>
412        </ul>
413      </div>
414
415      <div class="release">
416        <div class="meta"><span class="ver">v1.5.2</span><span class="date">11 July 2026</span><span class="tag">Extension</span></div>
417        <h3>🎥 Never lose a recording when storage is full</h3>
418        <ul>
419          <li>If your free video storage is full and no cloud is connected, a new recording is now <b>saved to the reporter's own computer</b> and the bug is still filed — nothing is lost.</li>
420          <li>The reporter sees a clear heads-up, and admins get a dashboard banner prompting them to connect Google Drive or OneDrive.</li>
421        </ul>
422      </div>
423
424      <div class="release">
425        <div class="meta"><span class="ver">Data control</span><span class="date">11 July 2026</span><span class="tag">Privacy</span></div>
426        <h3>🗑️ Permanent delete & right-to-erasure</h3>
427        <ul>
428          <li>Admins can now <b>permanently delete</b> a bug or a video — including removing the actual video file from your Google Drive / OneDrive — separate from the reversible Archive.</li>
429          <li><b>Erase a person's data</b>: anonymize a user on request (GDPR / DPDP right to erasure) while their reported bugs stay as the workspace's records.</li>
430          <li>A rewritten, accurate <a href="/privacy.html">privacy policy</a> aligned with India's DPDP Act and the EU GDPR — including the services we use, data-subject rights, and a grievance officer.</li>
431        </ul>
432      </div>
433
434      <div class="release">
435        <div class="meta"><span class="ver">Free storage</span><span class="date">11 July 2026</span><span class="tag">Storage</span></div>
436        <h3>💾 100 MB of free video storage</h3>
437        <ul>
438          <li>Every free workspace now gets <b>100 MB of free video storage on our servers</b>
438 — record straight away, no setup.</li>
439          <li>Need more? Connect your own <b>Google Drive or OneDrive</b> and new videos go to your cloud. Settings shows how much of your 100 MB you've used.</li>
440        </ul>
441      </div>
442
443      <div class="release">
444        <div class="meta"><span class="ver">Security</span><span class="date">11 July 2026</span><span class="tag">Security</span></div>
445        <h3>🔒 Account & data hardening</h3>
446        <ul>
447          <li>Login tokens and access codes are now scrambled in our database, download links are short-lived, and there's a browser security policy and rate limiting.</li>
448          <li>Stronger minimum passwords, an admin <b>"Reset password"</b> action, and a <b>"Forgot password?"</b> helper on the login screen.</li>
449        </ul>
450      </div>
451
452      <div class="release">
453        <div class="meta"><span class="ver">Testing platform</span><span class="date">July 2026</span><span class="tag">Feature</span></div>
454        <h3>🎭 Turn any bug into a test</h3>
455        <ul>
456          <li>Export any reported bug as a runnable <b>Playwright test</b>, run it in your own CI, and let AI harden or heal it.</li>
457          <li><b>Regression guard</b>: mark a fixed bug to be watched — if it ever breaks again, it automatically reopens.</li>
458        </ul>
459      </div>
460
461      <div class="release">
462        <div class="meta"><span class="ver">Platform</span><span class="date">July 2026</span><span class="tag">Feature</span></div>
463        <h3>☁️ OneDrive, AI ticket-writing, and more</h3>
464        <ul>
465          <li><b>OneDrive</b> video storage (alongside Google Drive) and Microsoft sign-in.</li>
466          <li><b>AI ticket writer</b> that reads your screenshots to draft a clear title and summary.</li>
467          <li>Editable text labels on screenshots, all times shown in <b>IST</b>, and an admin panel for API keys and credentials.</li>
468        </ul>
469      </div>
470
471      <p style="color:var(--muted);font-size:14px;margin-top:36px">
472        Want something added? <a href="/contact.html">Tell us</a> — or
473        <a href="/signup.html">create a free workspace</a> to try it all.
474      </p>
475    </div>
476  </main>
477
478  <footer>
479    <div class="wrap">
480      <span>🐞 Bug Reporter — free bug reporting for teams</span>
481      <span><a href="/">Home</a> · <a href="/help.html">Help</a> · <a href="/contact.html">Contact</a> · <a href="/privacy.html">Privacy</a></span>
482    </div>
483  </footer>
484<script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495" integrity="sha512-iIg7k2xntmwu6/uSb5tpc/hySgZc4eoL31yB29W6tJFo2akwjPWcEqnCEdJvGexCL0KEQwVYv5BlowfhVz26hg==" data-cf-beacon='{"version":"2024.11.0","token":"97dcb4b9e0794148bb206a4c2c066651","r":1,"spa":2}' crossorigin="anonymous"></script>
484
485</body>
486</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.