Issues and Lifecycle Timeline¶

The Issues page shows the current issue set known to FastSLA. Use it to inspect operational state and open issue explanations.

Issue filters¶

The Issues page can filter by SLA state:

All
Breached
Running
Paused
Met
Excluded

You can also filter by source/current status and sort by columns such as issue key, priority, status, next target, and SLA state.

Example: finding open risk¶

To find issues that still need work:

Select Running.
Sort by next target.
Open the first issues in the list.
Check whether the lifecycle timeline shows a future target or a past missed target.

Use Paused separately. A paused issue may not need immediate team work, but it still needs follow-up if it has been waiting too long.

Pagination¶

The issue list is paginated. If you do not see every issue, check the page controls and active filters.

SLA state labels¶

Label	Meaning
Running	The SLA measurement is still open.
Paused	SLA time is currently paused.
Breached	The target was missed.
Met	The target was completed successfully.
Excluded	The issue does not count in SLA, often because Start was not observed.

Issue detail¶

Expanding an issue shows the explanation panel. It includes:

core issue fields
SLA target and result timestamps
lifecycle timeline
full event history
delete action for the issue

Lifecycle timeline¶

The lifecycle timeline starts at the first observed Start event. Events before Start are not plotted on the graph, but they remain visible in event history.

The graph shows:

SLA phase segments
significant status changes
dimmed no-effect status changes
target markers
breach markers
Now for running issues
Monday date markers for time scale

Example: response/resolution timeline¶

Start             Stop Response        Pause       Stop Resolution   Terminal
May 1 09:00       May 1 10:15          May 2       May 3 14:00      May 4

Read this as:

SLA started on May 1 at 09:00.
First response was reached at 10:15.
Time may stop while the issue is paused, depending on the policy.
Resolution was reached on May 3.
Terminal marks the issue as operationally finished.

Example: deadline timeline¶

Start                         Deadline target
May 1 09:00                   May 14 23:59

Deadline-mode issues show one deadline phase. There is no response phase because response is not measured for that priority/policy.

If the issue is still running, the graph can extend into the future to show the target. Now shows where current time is relative to the target.

Reading timeline labels¶

Important state labels such as Start and Deadline target appear above the graph.

Now and breach labels appear below the graph. Monday date markers also appear below the graph as a time scale.

Monday labels use compact month-day format, such as May 14. They are visual scale markers, not SLA events.

Deadline-mode timelines¶

If the issue is measured by a single deadline, the graph shows a single Deadline phase. Response is not shown as a measured phase.

Event history¶

Event history is the complete audit view. It may include source statuses that do not affect SLA.

Use event history when you need to verify exactly what FastSLA observed from the source.

Example: timeline versus event history¶

The timeline is optimized for SLA interpretation. It starts at Start and emphasizes SLA-changing events.

Event history is optimized for audit. It can show older events before Start and source statuses that do not change SLA state.

If the two look different, that is usually expected. Use the graph to understand SLA timing and event history to inspect every observed source event.

Deleting an issue¶

The issue detail danger zone can delete an issue. This is destructive and should be used only when the issue data is wrong or should no longer exist in FastSLA.