How to Track SLA Performance in Real-Time on Your Jira Dashboard

[#1]

A real-time gadget from RVS that brings live SLA visibility directly to your Jira dashboards — no extra reporting tools required.

Why SLA tracking matters

Service Level Agreements define the commitments your team makes to customers — response times, resolution windows, availability guarantees. Without visibility into how those commitments are being met, teams are reactive rather than proactive, and breaches go undetected until they've already damaged customer trust.

The SLA Dashboard Gadget brings that visibility directly onto your Jira dashboards, so your team can monitor, act on, and improve SLA performance without ever leaving Jira.

What the app does

Real-world use cases

Here's how different teams use the SLA Dashboard Gadget day-to-day — with real examples from the app itself.

Use case 1 - IT service desk — managing incident response SLAs

An IT operations team receives dozens of incidents each day across multiple priorities. Their SLA contract requires P1 incidents to receive a first response within 15 minutes and be resolved within 4 hours. Without a live view, agents only find out about a breach after it has happened.

With the gadget, the team pins a dashboard to their ops TV screen. They configure it to filter for their IT Support project, scoped to Incident issue types. The table shows every open ticket with live SLA countdown timers — green, amber, and red — so agents can see at a glance which tickets are at risk right now. A Time to Resolution chart grouped by priority gives team leads a daily visual of how well each priority band is being met.

Result: The team reduced P1 SLA breaches by catching amber-state tickets early and reassigning them before the clock ran out.

Use case 2 - Customer support — tracking Time to First Response across queues

A SaaS company's customer support team handles requests across three tiers: Free, Pro, and Enterprise. Enterprise customers have a contractual SLA requiring a first response within 2 hours. The support manager needs a live view to ensure Enterprise tickets are never deprioritised in a busy queue.

They set up two gadgets on the same dashboard: one filtered by customer tier = Enterprise using JQL, and a second showing the overall queue. The real-time SLA status column lets agents self-triage — they can see which Enterprise tickets are approaching their response window without needing a manager to flag them.

The Time to First Response chart, grouped by assignee, also helps the manager spot if one agent's queue is overloaded before an SLA breach occurs.

Result: Zero missed Enterprise response SLAs in the month after adoption, and faster self-directed prioritisation across the whole team.

Use case 3 - Operations team — preventing SLA breaches during high-volume periods

A managed services provider goes through predictable high-volume periods — Monday mornings, end-of-month billing windows, and product release days — when ticket volume spikes and SLA breaches are most likely. The ops lead needs early warning, not a retrospective report.

Using the gadget's JQL filter, they create a dashboard view scoped to tickets created in the last 24 hours with an open SLA status. During high-volume periods, this dashboard is front-and-centre. The gadget's live SLA counters tick down in real-time, making it obvious when a cluster of tickets all entered the amber zone simultaneously — a signal that a surge is happening and reallocation is needed.

The ops lead also uses the Time to Resolution chart grouped by request type to identify which categories consistently run close to the SLA limit, and feeds that into their staffing model.

Result: The team now proactively reallocates capacity during surges, cutting SLA-breach-related customer escalations in half.

Use case 4 - Engineering team — tracking internal SLAs on bug fixes

Not all SLAs are customer-facing. An engineering team has an internal agreement: Critical bugs must be acknowledged within 1 hour and resolved within 1 business day. These commitments are tracked in Jira Software — not Jira Service Management — and the team previously had no live visibility into whether they were on track.

Because the SLA Dashboard Gadget works with both Jira Software and Jira Service Management, the team adds the gadget to their engineering dashboard, filtered to Bug issue types with Critical or Blocker priority. They extend the table to include the Assignee and Fix Version fields, so the view shows who owns what and which release cycle the fix belongs to.

The Time to Resolution chart grouped by fix version gives the engineering lead a clear picture of SLA performance sprint-over-sprint — useful data for retrospectives.

Result: The team achieved consistent SLA compliance on Critical bugs for the first time, and the retrospective chart data led to a revised triage process for Blocker issues.

How to get started

1. Install from the Marketplace. Install directly from the Atlassian Marketplace and it appears in your Jira Cloud instance immediately.
2. Open or create a Jira dashboard. Navigate to Dashboards in the top navigation bar and open an existing dashboard or create a new one.
3. Add the gadget. Click Edit → Add a Gadget → search "RVS" → select the SLA Dashboard Gadget and click Add.
4. Configure your data source. Choose your project, filter by request type, priority, or issue type — or write a custom JQL query or point it at a saved Jira filter.
5. Set up your table and charts. Add extra fields to the SLA data table, then configure charts for Time to First Response or Time to Resolution with your preferred grouping dimension.
   
   

Configuration options at a glance

Option	Description
Project filter	Scope the gadget to one or more specific Jira projects.
Request / issue type	Narrow down to specific request types or issue types within a project.
Priority filter	Focus the view on high-priority or critical issues only.
JQL query	Use any custom JQL expression for precise, advanced filtering.
Saved Jira filters	Reuse existing saved filters from your Jira instance.
Table fields	Add extra Jira fields (assignee, labels, fix version, etc.) to the data table.
Chart metric & grouping	Choose Time to First Response or Time to Resolution, grouped by priority, assignee, request type, and more.

Resources

Jira Cloud only, partner-supported by RVS (Silver Marketplace Partner).

• Marketplace listing — Install the app from here
• Full documentation — Step-by-step setup guide from RVS