Reports¶

Reports show SLA compliance for a selected reporting window.

Reports are part of the Analysis area. Use Reports when you need contract follow-up, explanation, export, or a list of the issues behind the numbers.

Report window¶

Choose From and To dates, a project, and an SLA type. SLApulse calculates the report for that full date window using the selected project and current workflow rules.

The From date starts at local midnight (00:00). The To date includes the full selected day through 23:59.

Applied report scope¶

The fields in Report scope are a draft until you choose Load updated report. This lets you compare a different period, project, or SLA type without changing the numbers, issue pages, or export you are currently reviewing.

After loading, the page names the applied project, date range, and SLA type. Refresh applied report, pagination, and export all use that named scope. Loading a new scope returns to the first issue page and closes an open issue explanation.

Choose one of these SLA types:

All SLA types for both response + resolution and fixed-deadline issues.
Response + resolution for the two duration measurements only.
Fixed deadline for the single deadline measurement only.

Total eligible issues¶

Total eligible issues is the number of issues that count in the report after project filtering and SLA exclusion rules.

The card also names how many eligible issues use response + resolution and how many use a fixed deadline. This is a scope description, not a combined compliance rate.

Issues excluded because SLApulse did not observe a reliable Start event do not count.

Met percentages¶

SLApulse 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.

Response, resolution, and deadline always keep their own numerator and denominator. A fixed deadline has one result; response + resolution has two. SLApulse never combines their rates, even when All SLA types is selected.

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 pagination within the applied scope. It shows the SLA type on every row.

Response and resolution are shown as Not applicable for fixed-deadline issues. Deadline is Not applicable for response + resolution issues. Select the issue key to open or close its explanation panel, lifecycle timeline, and full event history; the rest of the row does not open the panel.

Export raw data¶

Use Export data when you need the issue-level data behind the report numbers.

Exports use the same applied dates, project, and SLA type as the page. They include all report issues in that scope, not only the currently visible page in the issue list. If you edit the scope fields without loading them, export still uses the scope named above the report.

Choose:

CSV when you need a general interchange format for integrations, archival, or tools outside Excel.
Excel (.xlsx) when you want a workbook for spreadsheet review, filtering, and contract follow-up.

The export is useful when you need to:

share report evidence outside SLApulse
reconcile report numbers in a spreadsheet
archive the issue-level basis for a contract period
investigate which issues contributed to met, missed, running, paused, or excluded counts

Both formats contain one row per report issue with:

issue key and project key
created timestamp, priority, and final status
source issue type and source status
first observation, SLA start, and latest update timestamps
whether the issue counts in SLA
response, resolution, and deadline status
response, resolution, and deadline target timestamps
SLA exclusion reason, stop timestamps, and measured response and resolution minutes
SLA measurement mode, deadline completion timestamp, and deadline day mode
breach exemption fields
the same explanation reason shown in SLApulse

CSV is the canonical data set: it uses English snake_case column names and UTC timestamps in ISO 8601 format. Excel uses the same columns and order, with typed booleans and local typed timestamps so sorting and filtering work naturally in Excel. The workbook also includes a metadata sheet with the applied report window, project scope, SLA type, export timezone, and generated timestamp.

The elapsed-minute fields show the accumulated time at the latest processed event. The response and resolution time fields show the final measured time when that measurement has stopped.

Exports do not include the full event history for each issue. Open the issue explanation panel when you need the complete timeline and source event audit trail.

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.
Use Export data if the findings need to be shared, archived, or checked in a spreadsheet.

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: Operations has fewer issues than Reports¶

This can be correct.

Command Center and Operations focus on current operational attention. They remove terminal work from live pressure and highlight active or paused issues that may still need action.

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.