# Filter Hygiene Representative Sample Summary

Sample notice: Representative deterministic sample - not tenant data
Generated: 2026-07-11T19:30:00Z
Last scan: 2026-07-11T19:29:30Z
Scan criteria: mode=full, filterName=any, owner=any, visibility=Any, privateFilters=excluded
Active cleanup view: All results
Corpus coverage: complete; 8/8 representative filters; 1 page

## Counts

- Representative filters: 8
- Cleanup need - high: 2
- Cleanup need - medium: 2
- Cleanup need - low: 0
- Cleanup need - none: 4
- Known direct Jira Software boards: 1
- Known incoming saved-filter references: 1
- Unknown due to supported-check failure: 1
- Preflight required: 7
- Blocked: 1

## Evidence boundary

- Direct Jira Software boards and incoming references from the accessible saved-filter corpus are supported evidence paths.
- Dashboard gadgets, Jira Service Management queues, standalone reports, automations, exports, and external consumers are unavailable or unchecked unless Jira returns specific evidence.
- None known means no relationship was found by the supported completed checks; it does not mean safe to delete.
- Failed, denied, partial, and unavailable evidence stay distinct. A failed required check blocks the destructive action.

## Destructive-action boundary

- Permanent deletion is limited to one reviewed filter per confirmation.
- Deletion repeats live preflight, requires typed DELETE, and cannot be undone by Filter Hygiene.
- Known or uncertain incoming saved-filter references block deletion.
- Exact undo is limited to eligible owner/share changes and stops if Jira no longer matches the expected post-change state or rejects restoration.