Tracking (personal)

DM a GitHub PR link straight to Queuebird and it starts tracking it just for you — it appears under TRACKING in your personal App Home. Nobody else sees it. Use it for any PR you want to keep an eye on, including ones nobody asked you to review.

Tracking also starts on its own when you paste someone else’s PR into a review channel: since you clearly care how it turns out, it joins your TRACKING automatically.

Stop tracking any time from the card — and if you change your mind, DM the link again and it comes back as a fresh watch, history intact. (One deliberate exception: your own PR that the team already tracks stays on the team card, where it lives under Your PRs.) Re-pasting a parked or hidden team PR doesn’t revive it either — a thread note points you to /qb parked instead.

Personal tracked rows are invisible to every team surface — they never appear in a team queue, never schedule team SLA jobs, and never show up in team stats. When a PR you’re tracking merges or closes, Queuebird sends you a one-shot DM so you can stop thinking about it.

If Queuebird was down (a deploy, a restart), it catches up on its own: PRs pasted while it was offline are tracked or routed on restart, with a fresh clock, going back up to 48 hours — intake channels are covered too, right down to a tagged paste’s team routing and an untagged paste’s confirmation prompt. A recovered PR behaves like a live paste in every way that matters, right down to the paster getting their own automatic TRACKING watch once the first GitHub update arrives. One deliberate difference: a recovered routed PR posts no arrival card in its destination queue channel — replaying a downtime’s intake must never flood a queue. (A disambiguation prompt left behind is still a live click, so answering it does post one.)