Repro

Bug reports that arrive ready to fix.

Repro is a bug tracker where every report arrives complete: steps to reproduce, logs, and the commit that likely caused it.

Used every day by 30+ engineering teams in private beta.

In private beta with teams at

Fixing the bug is the short part.

The long part is everything before it: asking for steps, searching logs, guessing which change broke it. Meanwhile, the same bug gets reported twice more.

Every report lands in one place. Slack messages, support tickets and production errors arrive here, already grouped by bug.

Open it and start fixing. Environment, logs and the suspect commit are attached before anyone has to ask.

A backlog that is already sorted. Every bug comes with a suggested severity and owner, and stays in sync with your tracker.

AAcme web

My bugs

Status

Needs info0
In progress2
Fixed18
Inbox 4 bugs
Grouped by bug
    • checkout is broken, any update?Slack2h
    • Customer can’t pay with a saved cardSupport1h
    • TypeError at checkout.ts:48Production2h
  • REP-127Avatar upload fails over 5 MB2 reports merged
  • REP-131Search flickers on back navigation1 report
  • REP-132Export menu overlaps the footer on mobile1 report

AAcme web

My bugs

Status

Needs info0
In progress2
Fixed18
/ REP-128
In progressSynced to Linear

Checkout fails with saved cards

3 reports merged · Opened 2 hours ago

Chrome 131 · macOS 15 · web v2.14.0

Severity
High
Owner
AAna

Steps to reproduce

  1. 1Log in as any customer
  2. 2Add an item to the cart
  3. 3Go to checkout
  4. 4Choose a saved card
  5. 5Press Pay

Suspect commit

a3f9c1eRefactor cart totals

Deployed 2 hours before the first report

cart/totals.ts

- total = cart.total
+ total = cart.total ?? sum(items)

Logs

TypeError: Cannot read properties of undefined (reading 'total')
at checkout.ts:48

AAcme web

My bugs

Status

Needs info0
In progress2
Fixed18
All bugs 20
Synced to Linear
BugSeverityOwnerStatus
Checkout fails with saved cardsREP-128 · 3 reports High A In progress
Search flickers on back navigationREP-131 · 1 report Medium L In progress
CSV export drops the last rowREP-125 · 5 reports High A Fixed
Avatar upload fails over 5 MBREP-127 · 2 reports Low M Fixed
Theme resets on reloadREP-122 · 1 report Low L Fixed

Severity and owner are suggested by Repro when the issue is created.

Three reports come in. One issue comes out.

  1. Reports come in from anywhere.

    Slack messages, support tickets and production errors land in one inbox.

  2. Repro merges the same bug.

    Three reports become one issue, with steps, logs and the suspect commit attached.


  3. Track it until it’s fixed.

    Status, priority and owner in one place, synced with Linear, Jira or GitHub Issues.

What’s inside every issue

  1. Summary

    The bug in one line, with its status and severity.

  2. Steps to reproduce

    Recorded as it happened. Nobody has to write them.

  3. Environment

    Browser, OS and app version, attached.

  4. Logs

    Console and network errors from the same session.

  5. Suspect commit

    The change most likely behind it, with its diff.

  6. Duplicates

    Every report of the same bug, merged here.

Teams that stopped asking for steps

“The first hour of every bug used to be questions. Now we open the issue and the steps, the logs and the commit are already there.”

Priya RamanEngineering manager, Northwind

“Three people report the same checkout bug and I get one issue, not three threads.”

Daniel OkoroTech lead, Tessera

41 min

saved per bug before anyone starts fixing.

Median across beta teams

1 in 3

reports is a duplicate, merged before it reaches the backlog.

Private beta, last 90 days

Bugs live in Repro. Your roadmap stays where it is.

Reports come in from Slack, your help desk and your error monitoring. Every issue syncs with Linear, Jira or GitHub Issues.

Get bug reports
that are ready to fix.

Repro is in private beta. We onboard a few teams each week.

We’ll email you when your spot opens.

Join 30+ engineering teams already in the private beta.