← All features
Alerts and absences

Three rules, yours to tune. Leave that is declared, not guessed.

A PR without review for two working days, a member with no event for five, a PR open for more than ten days. One email when an alert opens; it closes itself when the condition disappears. Declared absences never trigger a false alarm.

Alerts · open6 open · thresholds per team
◆acme/api-gateway #1284 open for 14dthreshold 10d · author truiz08:00
▲acme/web #872 no review for 4 working daysreviewer igarnier · threshold 2d08:00
▲svirtanen no event for 12 working daysthreshold 5d08:00
✓acme/api-gateway #1290 resolved: reviewed then mergedalert open 3dyesterday
—lea-m on vacation Oct 6 → 10declared · inactivity alert pausedSettings
1Set the thresholdsWorking days of the workspace, not calendar days. Drafts excluded. Each rule can be switched off.
2Declare an absenceMember, type, dates. The days are excluded from working-day counts and the inactivity alert pauses.
3Alerts close themselvesNo ticket to clear. When the PR is reviewed or the member is back, the alert resolves and says so.
One email per alertOr a daily summary instead, per manager.
Signals for a humanAn alert is a nudge to look, never an automated decision.
Visible in the appPush notification with a deep link to the alert.

Three rules, nothing else

A pull request without a first review for N working days. A member with no commit, PR, review or comment for N working days. A pull request open for more than N days. Each rule has its own threshold per team and can be switched off. There are no other rules and no composite score: each alert says one concrete thing you can act on.

Working days and absences

Thresholds count working days in the team’s time zone, with the week pattern you set. A declared absence, vacation, sick leave or parental leave, pauses the inactivity rule for that person and removes those days from their working-day count, so nobody is flagged for being on holiday.

How alerts live and die

An alert opens once, sends one email and one push, and appears in Notifications. It closes by itself when the condition disappears: the PR is reviewed, the member is active again, the PR is merged or closed. The resolution is logged with the time the alert was open, which is often the most useful number.

What alerts never do

They never rate a person. They never trigger an automated decision. They are sent to the team’s managers only, never to the member concerned and never to anyone outside the team.

Who it is for

For managers who would rather be nudged than monitor

Engineering managerUnblock reviews earlyA PR waiting two days is a message, not a Friday discovery.
Remote teamNotice silence kindlyFive quiet days prompts a check-in; declared leave never does.
Tech leadCatch long-lived branchesA PR open for ten days is where merge conflicts and lost context come from.
Questions

About alerts and absences

All answers →
  • The managers of the team, by email and push. Never the member concerned.
Other features