Validate Your Setup

Use this page before you trust reports or live SLA views.

The goal is simple: check a few real issues you understand. If those issues look right, the setup is usually ready for wider use.

Check one project first

Start with one project and a small import window.

1. Import 30 to 90 days of history.
2. Map observed statuses.
3. Set SLA goals and calendars.
4. Open a few known issues.
5. Compare SLApulse with the source system.
6. Fix mapping or filters before importing more history.

Pick sample issues

Choose examples that cover the normal workflow:

Sample	What it checks
One open issue	Current phase, target, and Now marker.
One resolved on-time issue	Successful completion and report inclusion.
One late issue	Breach explanation and target placement.
One paused issue	Waiting time and business-hours behavior.
One issue that should not count	Filters and missing Start handling.

Check each issue

Open the issue detail and check:

• the lifecycle starts at the first real Start
• pause periods match waiting states
• response appears only when response is measured
• deadline-mode issues show one deadline phase
• target markers match the configured priority
• no-effect statuses are visible but dimmed
• terminal status ends the active lifecycle

If one sample looks wrong, fix the setup before reviewing more reports.

Check reports

Create a report for the same period you imported.

Check:

• Total eligible issues matches what you expect
• met percentages use completed measurements only
• running and paused work is shown separately
• breached issues can be opened and explained
• closed issues can still appear in historical reports

Reports and Operations do not always show the same list. Operations shows current attention. Reports show historical measurement.

Check filters and calendars

Filters decide which issues count. Calendars decide when time counts.

Check:

• issue types and priorities match the contract
• internal tasks are excluded if they should not count
• business hours match the team's working schedule
• holidays or closure days are configured when needed

When to reset and reimport

Use Reset project data when old runtime data was built with wrong assumptions.

Typical reasons:

• status mapping was wrong during the first import
• the import window was too short
• issue filters were corrected after import
• you want one clean check before go-live

After reset, import the intended window again and check the same sample issues.

For normal follow-up, use reconcile or live webhooks instead of reset.