At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Selected space | Load stored page findings and resolutions | Space remediation rows | Source data must be available |
| Status filter | Show open, acknowledged, justified, closed, or all | Focused work queue | Status does not prove page correction |
| Page text filter | Match page, term, or finding context | Narrowed queue | It is not arbitrary full-text search |
| Finding owner | Display assigned responsibility | Visible ownership | Assignment does not grant page permission |
How it works
- Open Compliance Scanner.
- Select the governed space.
- Open Space Remediation Queue.
- Keep the status filter on open work.
- Filter by page or term when needed.
- Open each finding, assign ownership, correct the source, and rescan.
Example
A space has 35 findings. The queue lists open items before acknowledged, justified, and closed records. The governance lead filters for one policy page, assigns the content owner, and tracks the later rescan separately.
What this does not mean
The queue organizes stored findings. It does not calculate business risk, edit pages, approve term changes, or prove closure without a later scan and supporting evidence.
Related questions
Next step
Work open findings first, but review business criticality outside the queue.
View on Atlassian Marketplace