EPS SLA Compliance & Breach Tracking

Generated: 2026-03-02 11:39 EST | Data Source: JIRA | Tickets Analyzed: 878

Sprint Range:
Showing 0 of 0 sprints

SLA Definitions

Response Time

Time from ticket creation to first status transition, minus any time in “Waiting For Customer” status. Measures how quickly the team acknowledges the ticket.

Resolution Time

Time from ticket creation to last Done transition, minus time in pausing statuses. Measures total time to fix from the customer’s perspective.

Clock Pausing

The SLA clock pauses while a ticket is in “Waiting For Customer” status. This time is deducted from both response and resolution calculations.

Priority Thresholds

Blocker: 30m / 2h • Critical: 4h / 8h • Major: 16h / 24h • Normal: 24h / 48h
(Response / Resolution)

🔒 Data Privacy

This report displays only safe metadata fields (ticket key, priority, status, assignee, dates, product, component). No ticket summaries, descriptions, or comments are included. Click a ticket key to view details in Jira.

Data Source

project = EPS AND updated >= "2026-02-16" AND created >= -14d ORDER BY created DESC

Active SLA Dashboard

Open tickets with real-time SLA status. Click ticket keys to open in Jira.

Response SLA Achievement by Priority

Resolution SLA Achievement by Priority

SLA Breach Log

Tickets that breached response or resolution SLA, sorted by severity.

Achievement by Priority & Product

Root Cause Summary