Projects and Sources

Projects are where SLApulse connects to your source system and turns issue history into SLA views.

Admins set projects up in Setup. Members use the project data in Command Center, Operations, and Analysis.

Choose your first setup route

Create the project first. Then choose the route that gives you the data you need now. You can use both routes for the same project.

Receive live events

Use this route when new issue changes should arrive in SLApulse as they happen.

1. Copy the project webhook values from SLApulse.
2. Follow the setup guide for your source system. For Jira Cloud, use Jira Cloud Automation.
3. Send one test event or update one test issue.
4. Map the statuses SLApulse observes.

Import existing history

Use this route when you need existing issues in SLApulse or want to run reconcile later.

1. Add the source connection and its credentials.
2. Run Test connection.
3. Import a small date window.
4. Map the statuses you observe.

Finish the project setup

Whichever route you start with:

1. Set SLA goals and business-hours rules.
2. Check a few known issues and, when you have historical data, one report.
3. Confirm the project's next action in Command Center.
4. Use live tracking when the result looks right.

Start with one project. Add more when the first setup is easy to explain.

Project health

The Project Health panel tells you what to do next.

Common states:

State	Meaning	Next step
Ready to track	The project has enough setup to create live SLA issues.	Check sample issues, then monitor it in Command Center.
Needs attention	One or more setup steps are missing.	Follow the suggested action in the panel.
Collect only	SLApulse collects statuses but does not create live issues yet.	Map statuses, then switch to live tracking.

Source connection

The Source Connection area shows credentials, connection test status, import jobs, reconcile jobs, and the latest error.

A source connection is not needed just to receive live webhooks. Add one when you need source tests, historical imports, or reconcile jobs.

Use the guided action:

State	What to do
Missing credentials	Add credentials first.
Untested connection	Run Test connection.
Working connection with no history	Import history.
Failed job	Read the error, fix the cause, then retry.

Credentials are stored encrypted and used server-side for source tests, import, and reconcile.

Webhooks

Webhooks send new source events to SLApulse.

SLApulse first collects an accepted webhook in a durable inbox. It can then continue to process the event after a normal API or worker redeploy. “Accepted” means the event was safely collected; check webhook diagnostics to see its later processing result.

Use the values shown in the project setup panel:

1. Copy the webhook URL from SLApulse.
2. Do not edit the URL manually.
3. Copy the webhook secret when SLApulse displays it.
4. Add the secret as the X-Webhook-Secret header in the source system.
5. Send a test event or update a test issue.
6. Check webhook diagnostics if the event does not arrive.

The webhook URL and secret belong to one project. If you no longer have a copy of the secret, rotate it in SLApulse and update the source system with the new value. If you recreate a project, copy its new webhook values from SLApulse.

For Jira Cloud Automation setup, follow the step-by-step Jira Cloud Automation guide.

Import history

Use import when you want existing source issues in SLApulse.

A good first import is usually 30 to 90 days. It is large enough to show real workflows, but small enough to check by hand.

If the import window starts after an issue's real SLA start, that issue may be excluded. That is expected. SLApulse only counts issues where it sees a reliable Start.

Reading import progress

An import can show:

Imported history for 42/120 issues · 310 changes handled

Read this as:

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

Skipped changes are often fine. They may be duplicates or source statuses that do not change SLA state.

Reconcile

Use reconcile when the source has already been imported and you want to refresh it.

Action	Use it for
Import history	First setup or rebuild after reset.
Reconcile	Follow-up refresh using the current source setup.

For normal follow-up, use reconcile or live webhooks. Do not reset just to sync.

Reset project data

Reset project data clears imported/runtime data and keeps setup.

It removes:

• issues
• event history
• source checkpoints
• source job history

It keeps:

• project setup
• source connection setup
• webhook secret
• SLA rules
• status mapping
• issue filters

Use reset when the first import was based on wrong mapping, wrong filters, or a too-short date window. Reset is blocked while import or reconcile jobs are running.

Recommended rollout

Use this rollout for a calm setup:

1. Start with one known project.
2. Receive a few live events, import a limited history window, or both.
3. Map statuses from observed data.
4. Check a few known issues.
5. Check a report for the same period when you imported history.
6. Fix mapping or filters if needed.
7. Import a broader window when you need more history.
8. Repeat the same pattern for the next project.