Quality, now on every Brimble pull request.

Reviewing a pull request preview usually means screenshots in Slack, a link pasted into a ticket, and someone asking which build it was on. Brimble’s customers don’t have to work that way any more. Brimble has partnered with Quality to put feedback right on every preview, so teams review a change where it’s actually running.

Comment on the page, not about it

Every preview now carries Quality. Anyone on the team clicks the Quality button, points at the part of the page they mean, and leaves a comment pinned to that exact spot. Teammates reply in the thread, mention each other, and resolve it once it’s fixed. There’s no extension to install and nothing to set up per preview.

Context comes with every comment

Each comment carries a replay of what was happening on the page, with the console and network activity behind it, so an engineer can see the problem instead of reconstructing it from a description. When a thread needs to become work, it goes straight to Linear, Jira or Slack.

Feedback that follows the pull request

Every pull request gets a new preview URL, and that’s usually where feedback gets lost. Quality keeps the conversation on the page rather than the URL, so a comment left on one preview is still there on the next, labelled with the pull request it came from, like PR #42. Reviews pick up where they left off instead of starting over with each build.

Built for platforms

Brimble set this up once, through Quality’s partner API. Workspaces, projects and previews are created and cleaned up automatically as teams work, so its customers get collaboration without configuring a thing:

• Reviewers comment on the running page, not in a separate doc.
• Engineers get a replay and the full context with every comment.
• Conversations carry over from one preview to the next.

The same API is open to any platform that hosts previews. If you’d like Quality inside your product, get in touch.