QA shouldn't have to prove a bug exists, over and over again...
but here we are
this is our first major release of 2026, we've significantly improved how QA teams captures bugs and hand off repro steps with
@SamelogicAI
here's the problem we kept hearing:
you find a bug, you know exactly which element is broken, but by the time you write it up, screenshot it, and hand it off... something gets lost.
engineering opens the ticket and asks three follow-up questions anyway.
so now you can:
→ find the broken element directly on the page
→ hit record and capture your repro steps
→ create repro steps with 1 click
the element travels with the bug report. same selector, same state, same context. no guessing.
a few teams have been using the beta for the past 3 weeks and they're loving how easy it is to capture a bug and push it straight to Jira or Linear.
engineering reproduces on the first try instead of asking follow-up questions.
if you're doing QA and spend too much time proving bugs exist instead of fixing them, this might help :)