Coming soon · Bitbucket Cloud

Put an SLA on
code review.

PRs sit for days waiting on review and you can't even see it. SLAdar sets a review deadline, flags every stale pull request, and nudges the reviewer right on the PR — then shows you the compliance rate. All inside Bitbucket. No Slack, no data leaving Atlassian.

Runs on Atlassian No data leaves Atlassian Free tier planned

feature/checkout-totals → main BREACHED

Refactor checkout totals calculation

#482 · opened 2 days ago · reviewers alex, sam

First-review SLA4h 12m over

🔴 SLAdar — review SLA breached. This PR passed its review deadline. @alex @sam, this one needs attention.

The problem

Slow reviews, zero visibility.

Code review is the delivery bottleneck on most teams — a PR waits a day, two days, and nobody owns the delay. Native Bitbucket has no SLA concept and no per-person review stats, so leads can't even see how bad it is. The fixes that exist are Slack bots that drag your review data out of Atlassian, or enterprise analytics suites that are overkill for "no PR sits past a day."

How it works

Set it. Catch it. Report it.

A focused Forge app for Bitbucket Cloud — no external tool, no data leaving Atlassian.

🎯

Set a review SLA

One workspace policy: first review within N working hours, merge decision within M. Weekends excluded. Sensible defaults so it works on day one.

📡

Catch & nudge stale PRs

SLAdar tracks every open PR against the clock. When one goes at risk, then breached, it comments on the PR to nudge the reviewer — once per stage, never spammy.

📈

Report compliance

A dashboard of open PRs vs SLA (breaches in red, sorted by age) and a monthly "% reviewed within SLA" — the review-latency number your lead renews for.

Why SLAdar

The in-Atlassian, does-one-job option

Lives in Bitbucket, not Slack

The nudge lands as a comment on the pull request — where the reviewer already is. No separate Slack app to adopt, no context-switch.

Your code data never leaves Atlassian

Built on Atlassian Forge with the Runs on Atlassian badge. No external egress — the opposite of the Slack bots.

One job, done well

Not a heavyweight eng-analytics suite. Set a review SLA, catch the PRs that breach it, see your compliance rate. That's it.

A number your lead renews for

A monthly "% of PRs reviewed within SLA" report — the review-latency visibility native Bitbucket simply doesn't give you.

Be first to put your reviews on the clock.

SLAdar is in active development for Bitbucket Cloud. Drop your email and we'll tell you the day it lands on the Marketplace — no spam, unsubscribe anytime.

Put an SLA oncode review.