Projects and Sources

Projects are the main setup unit in FastSLA. A project defines where issue data comes from, which issues count, how source statuses are interpreted, and which SLA targets apply.

Project health

The Project Health section summarizes whether the selected project is ready to track SLA.

Common states:

• Ready to track: the project has enough setup to create live SLA issues.
• Needs attention: one or more required setup parts are missing.
• Collect only: incoming source statuses are collected for mapping, but live issues are not created.

Use collect-only mode when you want to observe statuses before deciding how to map them.

Source connection

The Source Connection area shows the current source status, credentials, last connection test, recent import/reconcile job, and latest error.

The guided action changes based on state:

• Missing credentials: add credentials first.
• Untested connection: test the connection.
• Working connection with no history: import history.
• Failed job: review the error and retry.

Credentials

Credentials are required before FastSLA can test the source or import history. Credential rotation is a secondary action because normal daily operation should not revolve around tokens.

After changing credentials, run Test connection.

Import history

Use import when you want to bring source issue history into FastSLA.

The import progress has two broad phases:

1. FastSLA scans source issues.
2. FastSLA imports issue history and applies relevant changes.

For sources that support issue counts, progress is issue-based. Changes/events are shown as supporting detail.

Example: reading import progress

An import can show messages like:

Imported history for 42/120 issues · 310 changes handled

Read this as:

• 120 source issues are expected from the source count.
• 42 issues have been handled so far.
• 310 source changes have been read and applied or skipped.

Skipped changes are not automatically bad. They often mean FastSLA saw a duplicate event, a no-effect status, or a source change that does not change SLA state.

Import date window

Use a date window when the source history is large or you only need a known period.

Example:

Need	Suggested action
Validate setup quickly	Import the last 30 to 90 days.
Produce a quarterly report	Import at least the quarter plus enough prior history to include Start events.
Rebuild after reset	Import the same window you want to validate, then inspect sample issues.

If the window starts after an issue's real Start event, that issue may be excluded because FastSLA did not observe the start.

Reconcile

Use reconcile when you want FastSLA to refresh source data using the current source checkpoints and date window.

Import is usually the first bulk load. Reconcile is usually a follow-up refresh.

Import versus reconcile

Action	Best for	Typical timing
Import history	Bringing existing issues into FastSLA.	First setup or after a reset.
Reconcile	Refreshing source data after history already exists.	Follow-up sync or operational correction.

Progress and job history

Running jobs are shown in the Sync area. The UI refreshes while jobs are pending or running.

Progress may be determinate or indeterminate depending on whether the source can provide a count up front.

The job history keeps recent import and reconcile results. Failed jobs show the error without hiding the rest of the source setup.

Source danger zone

The source danger zone contains destructive actions.

Use Reset project data only when you want to clear imported/runtime data for the project while keeping configuration. It removes issues, events, source checkpoints, and source job history. It does not delete the project configuration.

FastSLA rejects reset while import or reconcile jobs are pending or running.

Webhooks

The webhook secret identifies incoming source events for a project. If webhooks continue after a reset, new events can recreate runtime data.

If a webhook request fails, check source payload configuration and server logs. Empty or invalid webhook bodies are rejected.

Common source setup examples

Good first setup

1. Create project.
2. Add source connection.
3. Add credentials.
4. Test connection.
5. Import a limited date window.
6. Map statuses from observed source statuses.
7. Import a broader window.
8. Check Issues and Reports.

Reset and rebuild

Use this when imported data was based on wrong mapping or wrong filters:

1. Stop or wait for running source jobs to finish.
2. Use Reset project data.
3. Confirm mappings and filters.
4. Import the intended window again.
5. Re-check excluded issues and reports.

Do not use reset as a normal sync tool. It is a cleanup operation.