Tracks Bitbucket pull requests as code change objects in DevRev, links them to issues, and automates issue stages, review tasks, and stale PR reminders.

Your team's real progress lives in pull requests, but your planning lives in DevRev. This snap-in closes that gap: every Bitbucket pull request becomes a first-class code change object in DevRev, automatically linked to the issues it addresses. No copy-pasting links, and no status meetings to find out what shipped.

Features

Complete PR lifecycle tracking Every pull request is mirrored as a code change object with author, branches, repository, reviewers, commits, and status (Draft, Waiting for Review, Approved, Merged, or Closed), updated in real time from Bitbucket webhooks. After merge, lines added, lines deleted, and files changed are captured for change-size visibility. Automatic issue linking Mention an issue like ISS-123 in your branch name, PR title, or description, or use the /towards ISS-123 command, and the PR is linked to it automatically. Issue links stay in sync as the PR description evolves. Jira issue references can also be resolved when configured. Issue workflow automation

• Move issues through stages as PRs open, merge, or close – for example In Review on PR open and Completed on merge with /close
• Create review tasks for requested reviewers, closed automatically on approval or merge
• Track the latest code activity on every linked issue

Autonomous issue tracking Working on something without an issue? The snap-in can create one automatically when a branch or PR appears with no referenced work – titled and described from the PR, assigned to the author, and routed to the right part. Stale PR reminders Configurable inactivity reminders nudge linked issues when a PR has sat idle too long, so nothing falls through the cracks.

How it works

Connect your Bitbucket workspace and set the workspace slug in configuration. The snap-in registers the webhook automatically on activation, and commits, PRs, reviews, and merges flow into DevRev from that moment. Your developers keep working exactly as they do today.