Trigger Attribution Breakdown

A high escalation score can be driven by many different combinations of underlying signals. One project might be escalating primarily because of SLA breaches. Another might be driven by reopen surges. A third might have both. Understanding which signal is contributing most to the score tells you where to direct remediation effort.

What you can conclude

• If SLA breach rate dominates the score, capacity or prioritization is the problem — the team can't deliver within its commitments.
• If reopen surge dominates, quality is the problem — work is being closed prematurely and coming back.
• If stuck-issue growth dominates, workflow blockages are the issue — something is preventing issues from progressing.

How this chart works

Stacked bar chart showing weekly escalation score broken down by contributing signal per project: SLA breach rate, reopen surge, and stuck-issue growth. Each segment's size represents its proportional contribution to the total score. Select a project to see its weekly timeline; leave unfiltered to compare latest values across all projects.