#30 Report of the Week: Blocker Incident Tracker

[#1]

In this edition of our Report of the Week series, we spotlight a highly focused and insightful report: the Blocker Incident Tracker. This report is designed to help teams monitor critical incidents, ensure SLA compliance, and track the frequency of high-priority blocker issues.

This report lists high-priority incidents filtered to:

• ⚡ Incident issue type with "Highest" priority

• ✉️ Customer request types, response/resolution times, and created dates

• ⏱ SLA tracking metrics for both first response and resolution, including breach indicators

• ⏳ Elapsed time for first response and resolution SLAs

• ⌛ A custom measure: "Time till next blocker incident", which calculates the time between consecutive incidents

For the custom metric "Time till next blocker incident", the PreviousRowValue function (available in eazyBI Cloud and from version 6.5.0+ for Data Center) is used to find the previous incident and its creation date. Then, DateDiffMinutes calculates the time difference in minutes between two consecutive incidents, which is formatted into days, hours, and minutes.

The report uses conditional formatting to highlight in red any breached resolution or response time SLAs, making it easy to spot critical blocker issues at a glance.

💡 Blocker incident tracker helps teams to:

• ⌚ Monitor the frequency of critical incidents

• ⏱ Track SLA compliance for high-priority issues

• 🧰 Spot recurring blockers and reduce downtime

• ⚡ Take rapid action on urgent support items

Ready to get more control over your incident management?

Add the Blocker Incident Tracker to your eazyBI dashboard and make sure you're staying ahead of SLA targets and blocker trends.

Stay tuned for next week’s Report of the Week for more ways to turn your Jira data into real-world impact! 🚀