AviumStart free →
Avium SignalsTeam tier and above

Blocked & Stale — surface the work nobody flagged

Half your sprint is fine. A few tickets have been quietly stuck for a week. Avium tells you which ones — by age, with the reason — before standup.

Avium IntelligenceFriday, May 31

Sprint 24 is trending to miss — three things need you today.

  • Sprint 24 at 72% riskSprint Risk Forecast

    Pace is 12 points behind with 4 days left; 2 blockers unresolved.

  • Mike is committed to 132% of capacityOver-Allocation

    Re-balance 2 tickets before standup or the sprint slips with him.

  • APP-43 blocked 9 daysBlocked & Stale

    Oldest blocker on the board — make it the first item at standup.

Grounded in 4 Avium Signals — every claim traces back to a real signal, so the numbers are never invented.

The blocker that nobody calls a blocker

Engineers don't like saying they're blocked. It feels like failure. So the ticket sits — in review, in QA, waiting on a decision that never came — and the only signal is silence. The standup goes on. The burndown chart looks fine because the ticket is still 'in progress.' Three days later a different engineer mentions the blocker offhand and the whole team realizes nobody was tracking it.

The data was always there. Jira knew the ticket hadn't moved in seven days. Nobody asked Jira.

How teams try to catch blockers today

The methods that don't scale:

  • Manually checking the 'flagged' filter every morning — works if anyone remembers to flag tickets, which is the entire problem.
  • Tracking 'in review' columns by eye — your eye lies. A column with 6 tickets feels normal even if half of them have been there for a week.
  • Asking in standup 'anyone blocked' — only catches the engineers willing to say so.
  • Watching the burndown chart for inflection points — by the time the chart shows it, three days of work have already been lost.

How Avium Signals computes blocked & stale

Avium reads ticket activity (status changes, time logs, assignee changes) and applies a small set of rules:

  • Flagged: any ticket with the Jira flagged field set. Always surfaced regardless of age — the engineer asked for help; that's the loudest signal.
  • Stuck in review: ticket in a phase named 'review' (Avium's status mapping detects this) with no time-log activity for 7+ days. Configurable threshold.
  • Stale in-progress: ticket in an in-progress phase for 14+ days AND no activity for 7+ days. Catches the 'started, then forgotten' pattern.
  • Sorted by age descending — the oldest blocker is the first thing to discuss at standup. That's the agenda.

Who reads this Signal

Scrum masters
Your standup running order, sorted. Skip the warmup; lead with the oldest blocker.
Agile coaches
When you see the same ticket blocked across three standups, that's a coaching moment — escalation should have happened by day two.
Engineering managers
Knows who to unblock without asking. The list is on your phone before the team's daily.
VPs of engineering
Cross-team blocker count is one of the highest-leverage org-health metrics. If it's climbing, something structural is off (dependency on a slow team, an external vendor, a single point of failure).

See your stuck work

Free tier surfaces blocked + stale tickets in real time once your work management tool is connected (Jira today, more integrations on the way). Threshold configurable. Avium Intelligence on Business turns the list into a prioritized briefing that names who to escalate to.

Start free — no credit card →

Related Avium Signals

Sprint Risk Forecast
Stop finding out at sprint review. Avium Signals reads your Jira data — or any work management tool — and forecasts which sprints are about to miss — and why.
Time in Status
Your team isn't slow. Your tickets are sitting somewhere. Avium tells you which somewhere.
Hand-off Cost
A ticket assigned to one person ships fast. A ticket that's been reassigned three times takes 4× longer and reopens 2× as often. Avium counts every hand-off.