On-Call Registry

On-Call, in the main sidebar, shows every team and who's currently primary/secondary on-call for it. It's its own root nav item, not part of the Reports section, since it's a live roster rather than a comparative/ranked panel.

Needs a PagerDuty connection — without one, the page shows an empty state linking to Settings → Integrations instead of a table.

How a team's on-call is determined

There's no separate step to map a PagerDuty schedule to a team. A team's on-call is whichever of that team's own members currently shows up as on-call in PagerDuty (matched by email, or a manual link from Settings → Teams). If a person belongs to more than one team, or is on-call via more than one PagerDuty escalation policy, the page shows the first match per role — it doesn't merge or rank across multiple assignments for the same person.

Filtering

There's no date range or repo/Jira-project filter here — it always shows who's on call right now, not a historical window.

Access

Gated by its own standalone View On-Call Registry permission (onCall.view), not reports.view — see Granular Permissions for how standalone permissions like this fit into the model.