Reports¶
Reports show SLA compliance for a selected reporting window.
Use Reports when you need contract follow-up, explanation, or a list of the issues behind the numbers.
Report window¶
Choose From and To timestamps. FastSLA calculates the report for that window using project filters and current workflow rules.
Total eligible issues¶
Total eligible issues is the number of issues that count in the report after project filtering and SLA exclusion rules.
Issues excluded because FastSLA did not observe a reliable Start event do not count.
Met percentages¶
FastSLA reports compliance as met percentage, not breach percentage.
For each SLA dimension:
met rate = met / (met + breached)
Running and paused measurements are unresolved. They are shown as excluded from the percentage denominator.
Example: contract-correct compliance¶
If a report window has:
| Result | Count |
|---|---|
| Met | 87 |
| Breached | 13 |
| Running | 8 |
| Paused | 2 |
The met percentage is:
87 / (87 + 13) = 87.0%
The 10 unresolved measurements are shown as excluded. They are not counted as met and not counted as breached.
This is important when you review a contract period before every issue has completed.
Unresolved excluded¶
Unresolved excluded means the measurement is not complete yet. It is not counted as met or missed.
This is important for contract follow-up: a running issue should not make a completed-measurement percentage look better or worse.
Compliance bars¶
The compliance bars show:
- green: met
- red: breached/missed
- unresolved count as text, not as part of the bar
Hover over the bar segments to see counts.
Issue list¶
The report issue list supports sorting by column headers and filtering by SLA state.
Open an issue to see the explanation panel, lifecycle timeline, and full event history.
Example: explaining a missed target¶
When a compliance bar shows missed issues:
- Filter the report issue list to breached or sort by the relevant SLA status.
- Open an issue.
- Compare target timestamp, stop timestamp, and lifecycle timeline.
- Check whether pause periods explain any elapsed-time difference.
- Use event history if the timeline does not show the source event you expected.
This gives you the evidence behind the percentage.
Deadline dimension¶
Deadline compliance is shown separately. Projects using response/resolution mode may still show deadline as not applicable or empty depending on policy configuration.
Interpreting mismatch¶
If a report count looks unexpected:
- check whether the issue filter excludes the issue
- check whether a Start event was observed
- check whether the issue is still running or paused
- check whether the policy is deadline-mode or response/resolution-mode
- open the issue explanation panel and inspect event history
For a broader explanation of report math and operational versus historical views, see Understand SLA results.
Example: Overview has fewer issues than Reports¶
This can be correct.
Overview focuses on current operational attention. It removes terminal issues and highlights active pressure.
Reports measure what happened in a selected date window. A terminal issue can still be included in a report if it was eligible and completed inside the window.