Issue change states

Before reading states

Use this page after fingerprint comparison has matched a baseline run with a completed retest or scheduled monitoring run. Issue change states translate fingerprint comparison into customer-facing next actions. Do not send a summary, create remediation work or claim a fix worked until new, recurring, resolved and inconclusive states have been checked against evidence quality.

Review issue change states

Follow the path `Fingerprint comparison → Issue change states → Evidence review → Fix task, retest outcome, or monthly summary`.

1. Open /projects/{project}/monitoring after fingerprint comparison completes. Result: new_issue_count, recurring_issue_count and resolved_issue_count are based on comparable scan runs.
2. Start with recurring issues and open each changed finding before assigning work. Result: issue evidence confirms the same issue_fingerprint still appears in accepted scope.
3. Review new issues before sending alerts or summaries. Result: a newly observed fingerprint is checked for severity, affected URL and evidence quality.
4. Review resolved issues before claiming a fix worked. Result: the previous fingerprint is absent and the comparison scan has enough evidence to support the resolved state.
5. Move inconclusive items to the inconclusive evidence path instead of calling them fixed or new. Result: missing artifacts, changed scope or unavailable fingerprints remain visible.
6. Choose the next automated action from the state. Result: recurring findings go to fix tasks or ticket export, retest results go to Retest outcomes, and monitoring summaries use Monthly summaries.

State meanings

Use state labels as routing decisions, not just report counters.

• New issue means the current comparison run has an issue_fingerprint that was not in the baseline run.
• Recurring issue means the same issue_fingerprint appears again in the comparison run for the same accepted scope.
• Resolved issue means the baseline fingerprint is absent from the comparison run and the comparison has enough evidence.
• Changed evidence means the fingerprint is the same, but severity, URL, duplicate count or artifacts changed enough to inspect details.
• No issue change means the comparison did not produce a customer-facing state change for that fingerprint.

Blocked or inconclusive states

Do not convert these states into resolved, recurring or new claims.

• Inconclusive comparison means do not claim resolved until enough evidence exists.
• Comparison incomplete means comparison_scan_run_id is still running, failed or unavailable.
• Missing fingerprint means issue_fingerprint is not reliable enough for state routing.
• Changed accepted scope means the current scan did not cover the same authorized page set.
• Evidence incomplete means screenshot, HTML, console or network artifacts are missing for the claim.
• False-positive review pending means customer or reviewer context must settle before routing remediation.

Continue by state

Recurring states continue to Fix tasks or Ticket-only fallback when connected access is unavailable. Retest-driven states continue to Retest outcomes. Monitoring-driven states continue to Monthly summaries after the state list is evidence-backed. Use the related Inconclusive evidence page when any state depends on missing artifacts, changed scope or unavailable fingerprints.