IFS Service Desk Dashboard

Metrics

Last Updated

—

Central time

All-time tickets

—

Full IFS-related ticket count

All-time resolved

—

Currently Done/resolved

Last 30 days created

—

Current rolling activity

Last 30 days resolved

—

Current rolling activity

Highest-volume window

—

84 tickets created

Reporting windows

A concise leadership view of three rolling timeframes plus all-time performance.

Window	Created	Resolved	Open	Median resolution	Resolution rate
Loading live API data…

Recurring and critical issues

Recurring themes are approximate summary-keyword buckets from the past 30 days. Critical queue is aggregate only.

Recurring themes

#	Theme	Tickets
Loading live API data…

Critical queue snapshot

Metric	Value
Loading live API data…

Open priority	Tickets
Loading live API data…

High / Highest tickets

Current open High and Highest priority IFS-related tickets from Jira.

Issue Key	Summary	Current status	Priority
Loading live API data…

Backlog age expectations

Tickets	Ticket age	Classification	Expected action
—	3–5 business days	Aging	Technician reviews status and provides an update
—	6–10 business days	Backlog	Review ownership, blocker and next action
—	11–30 business days	Aged backlog	Team lead review; escalation/closure plan required
—	30+ days	Critical/stale backlog	Management review; resolve, close, escalate, or formally document why it remains open

Monthly volume trend

Created tickets by calendar month across the full dashboard dataset.

Loading live API data…

Last 30 days IFS ticket volume by location

Created tickets by Jira Location field for the current rolling 30-day window.

Loading live API data…

Top request types

Highest-volume service categories across the rolling dataset.

Loading live API data…

Top issue types

Work item classification by volume.

Loading live API data…

Priority mix

Executive snapshot of demand severity across the rolling dataset.

Loading live API data…

Executive takeaways

The last 30-day window reflects active throughput, while the prior rolling windows provide trend direction. Backlog is shown separately from window-open counts because created-minus-resolved within a reporting window is not the same as current operational backlog.