Running a scan

Before you start

The first scan uses the configured review threshold and cost assumptions. Free uses a fixed 90-day review signal and a bounded user analysis. Pro can use a custom threshold, custom cost assumptions and the complete available inventory.

The scan reads Jira data and writes only License Radar’s own analysis records. It does not change Jira while it runs.

What the progress means

The scan reads the supported user and application-role inventory, reads the bounded issue fields needed for observable activity, classifies the records and calculates the configured estimate. The interface keeps the current stage and coverage visible while work is in progress.

If you reload the Jira page, the app checks the stored scan state and resumes polling the same scan rather than starting a duplicate job.

Scan outcomes

COMPLETED

The requested stages finished and the result can be reviewed. Check the coverage summary and evidence limits before using the estimate.

PARTIAL

Some stages completed but another stage could not finish, for example when Jira issue activity was unavailable. The interface identifies what was read and what could not be analysed. Treat totals from a partial scan as incomplete; users without an activity signal are not converted into savings candidates.

FAILED

The scan could not produce a reliable result. The error explains whether the cause was authentication, permissions, rate limiting, a temporary Jira error or another unavailable dependency. A failed scan is not an empty result and must never be read as zero review candidates.

A safe review sequence

1. Wait for COMPLETED, or read the limitation attached to PARTIAL.
2. Check analysed users and scan coverage.
3. Open the strongest candidates and inspect their evidence.
4. Record a decision only when the available evidence is sufficient for your internal process.
5. Use History and Verify after a later completed scan to compare results.