Incident Resolution Time (MTTR)(3.4.8)

This visual shows the full distribution of how long issues take to reach their first delivered resolution, from creation to the first closing status that counts as delivered under your organization's terminal-status settings (a MetaFrazo default reading of the status name applies until you configure one) — split into two cohorts: issues resolved without reopening, and issues that were reopened at least once before final resolution. Issues discarded or canceled without delivery are kept in the data with their own disposition and are not counted as resolutions.

Mean Time to Recovery (MTTR) is usually reported as a single average. This view shows the distribution behind it, so a fast median and a slow tail can be seen together.

What you can conclude

• A wide distribution (a large gap between median and P90) means resolution times vary widely: some issues are resolved quickly while others take much longer.
• A large gap between the direct-resolution and reopened cohorts shows, in days, how much longer the reopened issues took to reach their final resolution.
• A tight distribution concentrated at the short end for direct resolutions means most of those issues were resolved in a similar, short time.

How this chart works

Histogram showing resolution time distribution split into direct-resolution and reopened-at-least-once cohorts. Shows median and P90 markers for each cohort.

Teams preparing a NIS2 review commonly bring the resolution-time distribution rather than a single average.