Connectors: a Report Becomes a Jira Issue, or a Card Your Channel Can Triage

A bug report is only worth what it saves the person who has to fix it, and until yesterday everything stopped one step short of where that person works. The report was complete, and somebody still had to copy it into Jira by hand.

Three destinations landed: Jira Cloud, Linear and Slack, alongside the plain signed URL from the day before. They live under Connectors in the dashboard.

File it into your tracker

Open a report, choose the tracker, and it becomes an issue there. The key it was given is shown on the report from then on, so the two are linked in both directions rather than living in one person’s memory.

If the project refuses the create - wrong permissions, a required field, a project that no longer exists - the report says so in a sentence, rather than failing quietly.

Or into a channel

Slack takes the four report events: a report arriving, its status changing, its severity changing, and somebody opening it for the first time.

What arrives is a card rather than a notification. A line of text with a link is worth almost nothing, because whoever reads it still has to open the report to find out whether it matters. The card carries the page it happened on, who reported it, the severity and status, how many requests failed, the first console error if there was one, and the screenshot. Somebody scrolling the channel can decide whether to care without opening anything.

If a delivery fails, the connector log shows the error. You should not have to notice an absence.

The report page now shows both halves at once

Clicking a console line or a failed request moves the recording to that moment. It is the thing that most distinguishes a report from a screen recording, and it was easy to miss, because the recording sat above the tabs - so anybody who had scrolled down to read the console was moving a player they could no longer see.

The recording and the evidence now sit side by side, with a divider you can drag to give either one more room. On a narrow screen they stack.

There is also a way to show a report in full to whoever holds the link. The trimmed-down view is right for a bug sent to a stranger and wrong when the report is a demonstration, or when it is going to a contractor or a client you would rather not create an account for.

Reading and writing are separate permissions now

If you have connected an agent to your reports, it used to be that read access was enough to move one - and moving a report to resolved emails the person who filed it.

Those two writes now need a permission of their own, granted separately. An agent given read access can list, search and open reports, and cannot change anything or send anybody a mail. We wrote on Tuesday about why that gap was worth closing.

We ask before a tracking tag runs

Our analytics and advertising tags used to run on the strength of a setting alone. There was no consent step anywhere on the site.

There is now, and the tags wait for it. It is the law in a fair part of Europe, and it should not have taken a legal argument to make the case.

Smaller things

• Sign in with Apple, alongside the five other ways to sign in.
• We removed a text editor that carried an unfixed security advisory rather than keep it.
• A new account gets a proper welcome however it was created, not only through the sign-up form.
• A report attributed to a domain by its tag is now kept for that domain’s retention window, like every other report on it.