At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Selected governed space | Load completed scan records | Chronological scan history | Only retained records appear |
| Scan date and glossary revision | Bind the result to its policy state | Comparable scan identity | Different scopes should not be compared as equal |
| Page and finding counts | Compare recorded outcomes | Trend signal | Counts do not explain cause |
| Page or glossary change | Run a new scan | Later evidence point | Prior evidence remains historical |
How it works
- Open Compliance Scanner.
- Select the governed space.
- Open Space Scan History.
- Compare scan date, findings, pages, and glossary revision.
- Open related page status and finding evidence.
- Run a new scan after material content or glossary changes.
Example
One scan shows 20 findings across 60 pages. A later scan shows 8 findings across the same 60 pages and the same glossary revision. That is a useful change signal. Reviewers still inspect finding records before claiming remediation success.
What this does not mean
History is not a causal analysis or certification. Comparisons can be misleading when page scope, glossary revision, access, or scan completion differs.
Related questions
Next step
Compare like-for-like scans and inspect the underlying findings.
View on Atlassian Marketplace