Skip to main content

Scans

The Scans page starts a scan run, shows the latest run, and lists the scans that came before it.

Starting a scan​

Choose a saved scan configuration and select Start scan. The selected configuration defaults to Default Full Scan when available, otherwise the first saved configuration. The scan reads Jira content through the API only and never edits, comments on, or deletes anything in Jira.

If the configuration restricts allowed scan windows, starting it outside those windows is refused and the message names the next time a window opens. A scan that has already started always runs to completion.

The active detection rule definitions are snapshotted before workers begin. Rule edits made during a run apply to the next run, and a paused or failed run continues with its original snapshot after resume or restart.

A configuration can also start scans by itself on a cron schedule, so routine scanning does not depend on anyone remembering.

Monitoring​

The Scans page shows the latest scan status and headline metrics, with earlier runs listed as Scan history below it. Open a scan for its detail page:

  • Status and current progress
  • Scanned and skipped issue counts, finding count, and error count
  • Scanned and skipped attachment counts, when attachment scanning was enabled
  • Current phase, start time, elapsed time, estimated remaining time, workers actually scanning against the configured maximum, and current throughput
  • Configuration ID, worker count, and throughput limit

Skipped issues and skipped attachments are counted separately from errors. A finished run with skips, errors, or a warning is labelled COMPLETED WITH GAPS.

Controlling a running scan​

The scan detail page enables only valid actions for the current state:

  • Pause - available while a scan is running
  • Resume - available while a scan is paused
  • Cancel - available while a scan is running or paused

A failed scan can be resumed from its last checkpoint rather than restarted, without duplicating findings. All state transitions are audited.

Exporting a scan​

Every scan run can be exported as CSV - one row per finding, metadata only, no matched values. See CSV export.