Skip to content

Issues and Lifecycle Timeline

The Issues page shows the current issue set known to SLApulse. Use it to filter the set, see which SLA type applies to each issue, and open a detailed explanation when you need it.

Issues is part of the Analysis area. It is not the primary triage surface. Use Operations when you need to decide what to work on now. Use Issues when you need the SLA target, timeline, event history, and explanation behind an issue.

Issue filters

The Issues page applies the selected filters together. Choose a project, SLA status, text in the source/current status, and SLA type, then select Apply filters. Clear all filters returns the list to its standard scope and the first page.

You can filter by active project:

  • All projects
  • one active project

You can filter by SLA type:

  • All SLA types
  • Response and resolution
  • Fixed deadline

You can filter by SLA state:

  • All
  • Breached or at risk
  • Breached
  • Running
  • Paused
  • Met
  • Excluded

Breached or at risk is the operational monitor scope. It contains SLA-relevant, non-finished issues with a running, paused, or breached measurement. It does not introduce a separate risk percentage.

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

Read the SLA type and next target

The list names the SLA type and the concrete target in every row:

  • For Response and resolution, the next target is Response until response is finished. It then becomes Resolution.
  • For Fixed deadline, the next target is always Deadline. Response and resolution do not apply to that issue.

The SLA-status pill includes text as well as colour, so the state is understandable without relying on colour alone.

Example: investigating open risk

To investigate issues that still need work:

  1. Select a project if you know where to start.
  2. Select Breached or at risk.
  3. Sort by next SLA target.
  4. Open the first issue keys in the list.
  5. Check whether the lifecycle timeline shows a future target or a past missed target.

For daily prioritization, start with Triage Board instead. Triage Board already groups active and paused issues by urgency.

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

Select an issue key to open or close its explanation. The rest of the row is informational, so sorting, page controls, and other controls remain available without opening a detail panel. Only one explanation is open at a time, and SLApulse loads it when you select its key.

The explanation panel 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 SLApulse 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 SLApulse.