Yesterday a report announced in Slack became something you can act on without leaving the channel.

The card already carried enough to decide whether a bug mattered. It now carries the two decisions that triage actually ends in: the status buttons, and the three severities in the same words the inbox uses. Press one and the report moves. The link to the full report keeps its place and stays the only coloured button on the card, because opening it is still the thing most people want.

If your team would rather the channel stayed a feed, there is a switch for that. A connected channel used to be able to change a report whether or not anybody had chosen that - the buttons simply arrived with the integration. Now a channel can be read-only, and the buttons are gone from the card rather than merely refusing when pressed.

Connecting is a normal install now

Jira and Slack are connected through their own install flows, with the badge each vendor asks you to use, instead of anything hand-rolled. The Jira control stays hidden until its install has actually finished, and a Jira connector says whose Atlassian account it runs on - which matters the day that person leaves.

Two more things on that page:

  • You can test a connector without waiting for a real bug to arrive. Paste a URL, write your signature check against the recipe on the same page, press the button, and see the delivery land or fail. The old answer was to wait and hope.
  • Each destination row says what kind it is, and webhooks have a card of their own rather than being the unnamed half of a list.

A connector is also keyed to the domain it serves, so one Slack workspace or one tracker can carry several of your sites without them colliding.

Extension 1.7.0 is in the store

The panel got better at explaining itself, which sounds small and is the difference between a person reporting a bug and giving up.

A refused recording now says what actually fixes it. Recording a tab needs the extension to have been invoked on that tab, and Chrome takes that permission back the moment the tab navigates - so the ordinary sequence spends it: open the panel, type the address of the page you meant to report, and the navigation you just performed has taken the permission with it. The panel used to suggest allowing the extension on all sites, which does not help with this at all, so following our own advice produced a second failure and no explanation. It now says what genuinely restores it, and why it keeps happening.

The reporter is told the screenshot is public before they take it, the same way they were already told about the recording. Whoever is capturing is the only person who knows whether the customer record open behind the bug matters.

And the browser name in a report is derived rather than assumed, so a report from Edge no longer says Chrome.

Session Replay

Free Chrome extension. One click on the page that is misbehaving captures the screenshot, the console and the network log, and hands you a link to paste into the ticket.

Get the extension

Captured credentials, everywhere this time

The report page and the HAR download have always dropped authorization headers, cookies and their relatives before rendering anything, because a share link needs no sign-in to read. The same report fetched through the API returned those headers as captured.

The same filter now applies everywhere a report can be read, which is what everyone reasonably assumed it already did.

Mail-sending endpoints - password resets, confirmations - are also rate limited per address and per IP now.

A report opened on a phone

The shared report page used to serve a phone exactly what it served a desktop, including an install link the Chrome Web Store cannot act on from a handset.

That was the wrong way round, because a phone is where a great many of these links get opened: somebody shares a report, the recipient taps it on the way somewhere. It now offers something a phone can actually do.

Alongside that: the status bar no longer collides with the header, the toast or the dialog on iOS, Android stops repainting the site because the colour scheme is declared, and the theme is settled before the page paints rather than flashing the wrong one.

Smaller things

  • A single network request can be downloaded as a HAR file through the API, not only from the report page.
  • The account menu comes out of the collapsed navigation on small screens and gets its own panel.
  • The Connectors page had a pass over what it says and the order it says it in.