Changelog

Added

• Jira integration — connect a Jira site once from the Admin Panel, and anyone in the company can file captured reports straight into it as issues. Owners and admins configure the connection; the API token is stored server-side and is never readable by the extension or by other members of the company.
• Multiple Jira projects with automatic routing — set up one destination per Jira project and give each the URL patterns it covers. A report picks its destination from the URL it was captured on, so a tester working across several sites gets the right project without choosing one. The reporter can still override it before sending, and that choice is remembered for that site.
• The send button names its destination — the Jira button shows the project key a report will be filed into, with a dropdown to pick a different one when the automatic choice is wrong. Previously the target was only visible in a picker further down the panel, which was easy to never see.
• A clear state when Jira is not set up — the send button is disabled with an explanation rather than failing on the click. Admins and owners are pointed at Jira Integration in the Admin Panel; everyone else is told what is missing and who can fix it, instead of being sent to a page they cannot open.
• “Check where a URL would go” — paste a URL in the Admin Panel and see which destination it resolves to, before anyone files a report against it.
• Jira connection test — a “Test connection” button confirms the site URL, account email and API token actually work and names the connected account, instead of the first real report being the thing that finds out.
• Screenshot and full report attached to the issue — every issue gets the annotated screenshot plus the complete BugBundler HTML report, so console logs, network activity and the DOM snapshot travel with the ticket rather than staying on the reporter's machine.
• Issues attributed to the person who filed them — the description names the reporter, and Jira's own Reporter field is set to their account where one can be matched with confidence.
• Per-destination access lists — a destination can be limited to named users, so a Jira project only receives reports from the people who should be filing into it.
• Confirmation before removing a report template, custom field or Jira destination — the trash icon now asks first, inline on the card, which turns red while it waits. A card you have just added and not filled in is still removed on the first click.
• Admin Panel opens in its own browser tab — Chrome closes the popup as soon as focus leaves it, which lost any half-finished admin form. The panel now opens as a full page instead.
• Company overview — the Admin Panel opens on a summary of the company: seat usage with a bar and free-seat count, subscription status with the renewal or trial-end date, and what is currently configured, with links straight to each section.

Changed

• Admin Panel redesigned for the full-page layout — sidebar navigation replaces the stacked accordions, with Company, Users, Invites, Custom Fields, Report Templates and Jira as sections. Every input is labelled, cards follow one layout, buttons show a spinner while saving, and figures load as skeletons rather than an ellipsis. The popup keeps its own compact layout unchanged.
• Site access is now requested when you enable a domain — the Chrome permission prompt used to appear later, during a capture, interrupting it. It now happens on the click that enables the domain, so enabling a site is a single decision with a single prompt. If the prompt is declined the domain stays enabled with network capture switched off, so a saved setting never promises data it cannot collect. A permission revoked later from chrome://extensions is now noticed too.
• Disconnecting Jira asks for confirmation — it deletes the stored token and every destination, so it now requires typing your email address, matching the rename-company flow.
• Report templates and custom fields save one at a time — each card has its own Save button instead of one button for the whole list, so saving one template no longer commits half-finished edits to another. Save stays disabled until that card has actually changed, and each card reports its own success or failure.
• Custom fields no longer have an icon — the icon was only ever visible in the Admin Panel’s own list and never shown to reporters, so it decorated nothing. Report templates keep theirs, which do appear when a reporter picks a template.
• Downloading a report is one click again — the download button is split, so the left half downloads and the caret offers the encrypted export. It matches the send-to-Jira control beside it, where the same shape means the same thing.
• Consistent keyboard focus — controls that fell back to the browser’s default blue outline (the Admin Panel sidebar, the add and remove buttons, the capture panel’s filters) now use the same focus ring as the rest of the app.
• Reports are substantially smaller — the DOM snapshot was being embedded four times over, and two of those copies were a download link that was larger than the snapshot it duplicated. It is now embedded once and the link is built on demand. Captured response bodies also had no limit on how much they carried between them; they now share a size budget and the oldest are dropped first, keeping each request's URL, status, timing and headers so the request itself is still there. The saving is largest on captures with a big DOM snapshot or many network requests.
• The report is locked while it is being sent or exported — a full-screen progress state names what is happening, and confirms when it is done. Building a report with a DOM snapshot and a few hundred requests takes long enough that it needs saying.

Fixed

• Enabling a domain could silently not save — the Chrome permission prompt closes the popup, which tore down the page before the setting was written. Reopening BugBundler asked you to enable the same domain again, even though the permission had been granted. The setting is now saved before the prompt is raised.
• Edits made during a send or export were silently lost — the screenshot annotation and the field values are captured at the moment the export starts, so anything drawn or typed while it ran stayed on screen while never reaching the file or the issue. The report is now locked for the duration.
• Clicking yourself in the members list — your own row navigated to the Account view, which in the admin tab also threw you out of the panel. The row is no longer a link.
• Admin errors shown twice — an admin error could appear both above the sidebar and inside the content pane at the same time.
• “Save” offering to save nothing — Custom Fields and Report Templates had Save permanently enabled, including on an untouched list. It is now enabled only when something has actually changed, with an “Unsaved changes” note so a disabled button is never a mystery.

Changed

• Free trial shortened to 30 days — new trials now run 30 days instead of 60. Trials already in progress are unaffected.

Fixed

• Popup opening too wide — the first time the popup was opened on a page it could appear about three times its normal width. The logo image had no explicit size until the stylesheet applied, so on a cold open it briefly rendered at full size and the popup was sized to match. The popup width is now locked from the first paint, so it always opens at its intended width.
• Missing icon on the "Enable all for this domain" button — the shield icon on the capture-enable prompt referenced an icon not included in the bundled set, so it rendered nothing; it now uses a bundled shield icon.

Added

• Microsoft sign-in — users can now sign in or create an account using their Microsoft account (personal, work, or school) via the "Sign in with Microsoft" button on the login screen.
• DOM Snapshot — captures the full rendered HTML of the page at the moment of the bug. Appears as a new tab in the overlay and exported report with a one-click Download HTML button, letting developers open the exact page state in a browser without needing access to the live environment.
• Custom fields per company — admins and owners can define up to 5 custom fields (dropdown or free text) from the Admin Panel. Fields appear in the capture overlay for reporters to fill in, and values are shown in the report's info table alongside URL, viewport, and other metadata.
• Network request/response details — network entries now capture full request/response headers and bodies for API calls (XHR/fetch), viewable via a "Show details" panel with separate Request/Response tabs on each row. Sensitive headers and matching fields inside JSON bodies are automatically redacted using the same rules as storage data.
• Copy as cURL — each network request's details panel now has a "Copy as cURL" button, producing a ready-to-run curl command for reproducing the request from a terminal.
• Performance metrics — captures Largest Contentful Paint, Cumulative Layout Shift, and Time to First Byte alongside every screenshot, shown as color-coded badges in the report's info table.

Changed

• Screenshot redaction redesigned — the three-mode selector (Off / Auto / Custom) is replaced with a simple on/off toggle. When enabled, password fields and common payment/sensitive inputs are always blurred automatically. An optional extra-selectors textarea lets you add CSS selectors on top, so custom rules no longer replace the built-in ones.
• Full localization pass — every remaining hardcoded English string across the popup, overlay, admin panel, settings, and exported report now goes through vue-i18n, so the entire UI is consistently translatable.
• Capture-data tabs polished — Console, Network, Storage, and DOM Snapshot each now show a distinct icon next to their title, and their header heights/styling are unified so switching between tabs no longer shifts the panel size or looks visually inconsistent.

Fixed

• Console and network capture reliability — fixed an issue where console errors/warnings and network requests could be missing from a captured report even when they were clearly present in the browser. Capture now begins automatically as soon as a domain is enabled for it, and site access is requested per domain instead of requiring broad access to all websites.
• Custom field label input — the field name/label input in the Admin Panel's Custom Fields editor could be squeezed to invisible width in the popup's narrow layout; it now sits on its own row.
• Custom fields order in exported reports — custom field values appeared after the Network row instead of between Severity and Website, inconsistent with the live overlay.
• Custom fields missing from Select Area captures — custom field values only appeared in reports created via Full Screen capture; Select Area capture never sent them through.
• DOM Snapshot reload — clicking a link inside the captured snapshot navigated the frame away with no way back short of switching tabs; a "Reload" button next to "Download" now resets it.
• Icons broken in exported reports — icons throughout the exported HTML report either failed to render or showed up at the wrong size, due to a missing component registration and a CSS rule scoped to a context the export never matches.
• DOM Snapshot leaking sensitive data — the DOM Snapshot capture included the raw, unredacted value of password/card/SSN/custom-tagged fields even when those same fields were correctly blurred in the screenshot. It now redacts the same fields, the same way.
• DOM Snapshot missing styling in exported reports — external stylesheets were serialized as a dead relative link that couldn't resolve once embedded elsewhere, so snapshots rendered completely unstyled. The actual CSS is now inlined directly into the snapshot.
• Account view "Back" button — always routed to a hardcoded destination instead of returning to whichever view the user actually came from.
• Popup crash on load — an unescaped character in a translated placeholder string could crash the localization engine during render, taking down the entire popup UI.

Added

• Severity tagging — tag each report with Critical, High, Medium, or Low. The badge appears in both the live overlay and the exported HTML.
• Auto-redact sensitive data — screenshot redaction with three modes: Auto (blurs password and payment fields), Custom (your own CSS selectors), and Off.
• Copy as Markdown — one click copies the report title and description as raw Markdown, ready to paste into GitHub, Jira, or Linear.
• Markdown list auto-continuation — pressing Enter on a list item continues the list; pressing Enter on an empty item exits it.
• Active template indicator — the currently applied description template is highlighted so it's always clear which one is in use.
• Export preview — preview the report before downloading in Static or Dynamic mode directly from the overlay header.
• Encrypted export — export reports as AES-256-GCM encrypted self-decrypting HTML files. Recipients open the file in any browser and enter the password to unlock.
• Update notification — the extension popup shows a one-time banner after an update with a link to the changelog. Dismissed on click and never shown again for the same version.

Changed

• Encrypted export page — the BugBundler logo now appears on the password-entry page instead of a lock emoji.
• Export button — the split download/dropdown is merged into a single unified button showing the download icon and a dropdown arrow.

Added

• Rename company — company owners can rename their company directly from the admin panel.
• Rename display name — users can update their display name from the account view, once every 24 hours.
• Free trial support — companies can be granted a time-limited free trial (default 60 days at the time, later reduced to 30) without Stripe billing setup. Access is revoked automatically when the trial expires.
• Trial status banner — company owners and admins see an amber banner with the trial end date during an active free trial.

Changed

• Create company button moved to the top of the account view action list, above change password and sign-out.
• Capture disabled banner moved above the capture buttons; buttons are now visually disabled when capture is not allowed for the current domain.

Fixed

• Login error notification (incorrect email/password) is now cleared automatically on successful sign-in.

Added

• Initial release of the BugBundler Chrome Extension.
• One-click bug report capture with screenshot, network requests, console logs, and metadata.
• Company admin panel for seat management and user invites.
• Jira and GitHub integration for direct bug report submission.
• Custom capture options per report.
• Offline-capable report drafting.