Alerts & Suggestions
SyncUp gives Scrum Masters two complementary signal streams.
1. Alerts tab
Section titled “1. Alerts tab”The Alerts tab shows every active alert across the sprint, in a table with Severity, Type, Message, and a Dismiss button. Dismissed alerts won’t reappear for the same sprint and same target object.
The six alert types
Section titled “The six alert types”| Type | Severity | Target | What it surfaces |
|---|---|---|---|
| Sprint Goal Risk | HIGH | Scrum Master | The projected completion is meaningfully below the sprint commitment, once there’s enough sprint time elapsed to project from. |
| Blocker Aging | HIGH | Scrum Master | An issue is flagged or blocked - one alert per flagged issue. |
| Scope Creep | MEDIUM | Scrum Master | Sprint scope has grown enough versus the earliest snapshot to be worth flagging. |
| Due Date Warning | MEDIUM | Issue assignee | An issue in the sprint is overdue or due within 24 hours. |
| Overload | HIGH | Scrum Master | One assignee is carrying substantially more work than the team average. |
| Milestone | LOW | All roles | Sprint reaches a notable completion milestone (such as 50%, 75%, or 90%). |
Each alert is deduplicated by (type, sprint, issueKey) - you won’t see the same Blocker Aging alert fire repeatedly for the same issue within one sprint.
Severity colors
Section titled “Severity colors”- HIGH - red badge
- MEDIUM - yellow badge
- LOW - neutral badge
The top two alerts (by recency) also appear at the very top of the Daily Brief tab as SectionMessages - so you don’t miss the most urgent signal even if you skip the Alerts tab.
Dismissing alerts
Section titled “Dismissing alerts”Click Dismiss next to any alert. It’s removed from the list immediately and won’t re-fire for the same (type, sprint, issueKey) until the next sprint.
2. Scrum Master “Suggestions”
Section titled “2. Scrum Master “Suggestions””Separate from alerts, the Scrum Master Daily Brief includes a 💡 Suggestions panel that proposes concrete moves. Up to three suggestions, refreshed live each time the brief loads.
The two suggestion types
Section titled “The two suggestion types”| Type | Example message | When it appears |
|---|---|---|
| Rebalance | “Move PROJ-401 from Ahmet to Ayşe (has capacity)” | One assignee is overloaded while a teammate has capacity. SyncUp picks a movable item from the overloaded person. |
| Unassigned | “3 unassigned items - consider assigning to Ayşe or Cem” | Any non-Done items in the sprint have no assignee, and there’s at least one person with capacity. |
Suggestions are generated each time you open the Daily Brief - they’re not stored. There’s no Dismiss / Snooze; just act on them or refresh later.
Alerts vs Suggestions
Section titled “Alerts vs Suggestions”| Alerts | Suggestions | |
|---|---|---|
| Where | Alerts tab + top of Daily Brief | Scrum Master Daily Brief |
| Stored | Yes (Forge SQL) | No (generated live) |
| Dismissable | Yes | N/A |
| Severity | HIGH / MEDIUM / LOW | Single tier |
| Types | 6 | 2 |
| Target audience | Per type | Scrum Master only |
| Generated by | Hourly trigger + on-page-load detection | On every brief render |
Personal alert sensitivity
Section titled “Personal alert sensitivity”Each user can tune how many alerts to surface in Settings → ⚙️ Preferences:
- Low - critical alerts only
- Medium (default) - important alerts
- High - all alerts
This is a per-user preference; it doesn’t affect what’s stored in the database, only what’s shown in your UI.
- Sprint Health - the score that underlies the Sprint Goal Risk alert.
- Configuration - alert sensitivity and other personal settings.