Documentation

Everything you need to install, configure, and operate PR Tracker for your team.

Quick links

• Getting started — Five-minute setup walkthrough
• Slack setup — Create a Slack app, connect via OAuth or manual
• Parsing rules — What PR Tracker recognizes in messages
• Outgoing webhooks — Stream events to Zapier / Make / Jira / Linear
• Troubleshooting — Common problems and fixes

Frequently asked questions

What does PR Tracker actually do?

It listens to your Slack channels for pull request URLs and keywords (approved, lgtm, +1,merged, deployed on PROD), and turns the chatter into a clean PR dashboard. No commands, no replies — just a passive listener.

Which Git providers are supported?

Bitbucket, GitHub, GitLab (including subgroups), and Azure DevOps. URL patterns are matched automatically.

How is a ticket marked “done”?

A ticket (e.g. WEB-1142) is done the moment any of its PRs has been both approved and merged. Sprint progress percentage is computed as (tickets done / tickets seen in this sprint) × 100.

Can I have multiple workspaces?

Yes. Each workspace is fully isolated. Members, Slack installs, sprints, and webhooks all scope to a workspace.

Do I have to use email/password sign-in?

Currently yes — that's the default. The schema supports adding OAuth providers (Google, GitHub, Microsoft) later via the NextAuth adapter without migrations.

Where is data hosted?

Postgres (Neon) and Vercel functions, by default. Slack tokens and webhook secrets are encrypted at rest with AES-256-GCM using a key in your ENCRYPTION_KEY env var.