ArdSaor

Filter Hygiene for evidence-led saved-filter cleanup

See what Jira can prove a filter affects before cleanup

Filter Hygiene separates concrete cleanup need, supported change impact, and action readiness. Scan saved filters Jira makes accessible to the app, see direct Jira Software boards and incoming saved-filter references, and preflight owner, sharing, or deletion changes before Jira is modified.

Install from Atlassian Marketplace View demo walkthrough Read documentation

Trials, purchase, billing, and exact pricing are handled on Atlassian Marketplace.

Built for Jira admins who need clear cleanup consequences—not another JQL results screen.

Last updated: 2026-07-11

What you get from the first scan

Scan result

Cleanup need, change impact, and action readiness stay separate across the accessible saved-filter corpus.

Impact evidence

Direct Jira Software boards and incoming references from accessible saved-filter JQL are named when Jira supports the evidence.

Guardrail

Unknown, failed, permission-denied, and unavailable relationships stay visible. Zero supported results is not a safe-to-delete claim.

Forge-builtBaseline app runtime and storage use Atlassian Forge. Data handling documentedPrivacy and retention details are published for admins. Support targetsSupport response windows and SLA terms are visible before rollout.

Inside Filter Hygiene

Production-verified Filter Hygiene impact review showing a direct Jira Software board dependency and explicit coverage limits; test data is redacted.
Direct Jira Software board impact See the boards Jira directly associates with a saved filter and what Jira cannot prove.
Production-verified Filter Hygiene impact review showing an incoming saved-filter JQL reference that blocks deletion; test identifiers are redacted.
Incoming saved-filter JQL reference Name accessible incoming saved-filter references before changing or deleting their target.
Production-verified Filter Hygiene impact review showing no returned supported relationship while overall impact remains unknown; test data is redacted.
Honest unknown impact Keep unavailable and unchecked relationships visible instead of turning zero supported results into a false safe result.

Why teams install Filter Hygiene

Jira exposes saved filters and JQL, but cleanup decisions are still scattered across ownership, sharing, validity, duplicate queries, downstream use, and direct edits. A filter that looks obsolete can still power a board or another saved filter.

Filter Hygiene puts cleanup evidence, supported impact, coverage limits, blockers, safest-next-action guidance, preflight, and exportable activity in one admin workflow.

What you can show

  • Progressive Full scan covers every saved filter Jira returns to the app and keeps incomplete scans partial and blocked from action.
  • Cleanup need, change impact, and action readiness stay separate instead of collapsing into one opaque risk score.
  • Direct Jira Software boards and incoming references from accessible saved-filter JQL are named when supported evidence exists.
  • Unknown, permission-denied, failed, and unavailable relationships remain distinct; zero supported relationships is not a safe result.
  • Owner/share actions use live preflight and exact compare-and-set undo where eligible.
  • Permanent deletion is one filter per confirmation, repeats impact review, requires typed DELETE, and cannot be undone.
  • CSV/Markdown exports and Recent Activity preserve the evidence trail.

Compared with native Jira cleanup

Need Native or manual path Filter Hygiene
Native JQL and filter search Jira exposes queries and results, but not one cleanup decision record. Filter Hygiene separates cleanup need, supported impact, and action readiness.
Dependency review Admins check boards and dependent filters across separate surfaces. Filter Hygiene names direct boards and incoming accessible saved-filter references, with explicit limits.
Direct edits Changes can happen without a live impact record or exact restore check. Preflight keeps owner/share changes reviewable and deletion one-at-a-time.
Ad hoc reporting Managers or security reviewers get screenshots or partial exports. CSV/Markdown exports preserve scan findings, coverage, decisions, and Recent Activity.

Sample - demo walkthrough

Demo walkthrough: saved-filter scan, cleanup queue, and export review

A screenshot-led walkthrough using representative, production-verified Filter Hygiene UI and sanitized data to show cleanup triage, supported impact, coverage limits, one-filter delete preflight, Recent Activity, and supporting exports.

Download demo walkthrough Buyer-facing PDF that explains how the app works with real app screenshots and clear remediation boundaries.
Download supporting exports and manifest
  • Scan CSV: Representative sanitized scan export with cleanup need, supported impact, coverage, action readiness, and no tenant account IDs or URLs.
  • Cleanup summary Markdown: Representative summary with concrete cleanup findings, supported relationships, unavailable paths, and deletion boundaries.
  • Manifest JSON: Bundle file names, sizes, SHA-256 hashes, screenshot boundaries, and compatibility aliases.
Scope limit: The walkthrough demonstrates the production-verified UI with representative sanitized data. Direct boards and incoming accessible saved-filter references are supported; unavailable relationships are not inferred.
Filter Hygiene walkthrough preview showing cleanup need, supported impact, coverage limits, one-filter deletion preflight, and export evidence with representative sanitized data.
Representative data is visibly labelled. The UI and action boundaries are production-verified; the sample does not prove customer remediation.

Fit and boundaries

Best for: Jira admins who need clear cleanup consequences, supported dependency evidence, and guarded changes—not another JQL results screen.

Not for: A full Jira configuration-management, backup, migration, rollback, dashboard-management, or complete dependency-discovery suite.

Where it fits

Use Filter Hygiene when Jira already exposes the saved filters and JQL, but admins still need one defensible view of cleanup need, supported impact, coverage limits, and the safest next action.

Use cases

  • Review broadly shared filters that may need narrower visibility.
  • Find filters owned by inactive or missing users.
  • Identify invalid JQL and exact duplicate normalized queries.
  • Reassign ownership during team or admin transitions.
  • See direct Jira Software boards and incoming saved-filter references before a change.
  • Delete one reviewed obsolete filter only after live supported-impact checks, explicit limitations, and typed confirmation.
  • Export cleanup records for governance reviews.

Core capabilities

  • Progressively scan the complete saved-filter corpus Jira makes accessible to the acting user and label incomplete scans as partial.
  • Separate Cleanup need, Change impact, and Action readiness instead of relying on an opaque score.
  • Validate JQL with Jira, group exact normalized duplicates, and surface concrete ownership, sharing, description, and available-use evidence.
  • Show direct Jira Software boards and incoming references from accessible saved-filter JQL while keeping unsupported relationships explicit.
  • Stage cleanup and run live preflight before owner, sharing, or one-filter deletion writes.
  • Use exact compare-and-set undo for eligible owner/share changes; deletion cannot be undone.
  • Export CSV or Markdown evidence and review Recent Activity.

Typical workflow

  1. Scan the accessible corpus

    Run a criteria scan or progressive Full scan and keep partial coverage visible.

  2. Review cleanup need

    Inspect concrete owner, sharing, JQL, duplicate, description, and available-use evidence.

  3. Review impact

    Check direct boards and incoming saved-filter JQL references; keep unavailable and failed paths distinct.

  4. Stage the next action

    Add reviewed filters to a controlled cleanup queue instead of changing Jira directly.

  5. Run live preflight

    Check current owner, sharing, validity, supported dependencies, blockers, warnings, and undo eligibility before writes.

  6. Export the record

    Keep CSV/Markdown evidence and Recent Activity for managers, security teams, or auditors.

Security, privacy, and support

  • Filter Hygiene uses Jira filter metadata, owner/share data, direct board relationships, and accessible saved-filter JQL for governance workflows.
  • Writes are limited to supported filter ownership, sharing, and explicit deletion actions selected by an administrator.
  • Permanent deletion is one filter per confirmation, repeats the live impact check, requires typed DELETE, and cannot be restored by Filter Hygiene.
  • Eligible recent owner/share changes use exact compare-and-set undo and stop if Jira state has changed.
  • Recent activity captures before and after summaries, failures, and exportable records.
  • App data is stored in Forge storage.

Operational links

FAQ

Will Filter Hygiene delete filters?

Yes. Admins can delete exactly one reviewed filter after a repeated live impact preflight and typed DELETE confirmation. Deleted filters cannot be restored by Filter Hygiene.

What dependency coverage is supported?

The app checks direct Jira Software boards and incoming references from the accessible saved-filter corpus. Dashboard gadgets, JSM queues, standalone reports, automations, exports, subscriptions Jira does not return, and external consumers remain unavailable or unchecked.

Does zero supported impact mean safe to delete?

No. Zero returned board or saved-filter relationships is not proof that a filter is unused or safe to delete. Unsupported and inaccessible relationships still require review.

Can admins preview changes?

Yes. Cleanup actions use live preflight so admins can review current evidence, blockers, warnings, and exact-undo eligibility before applying a write.

What evidence can be exported?

Recent Activity records who initiated actions, before and after owner or share summaries, deletion status, failures, and exportable CSV or Markdown reports.

Does it replace DriftGuard?

No. Filter Hygiene cleans up saved filters. DriftGuard monitors selected board and filter configuration changes over time.

Install from Marketplace

Review saved-filter impact before cleanup

Run a Full scan, turn concrete cleanup evidence into a staged action, and see what remains unknown before anything changes.

Open Marketplace listing Pricing View demo walkthrough

Related ArdSaor apps and solutions

DriftGuard screenshot from the Atlassian Marketplace listing showing Jira board and filter drift monitoring.

Jira configuration drift

DriftGuard

Catch risky Jira board and saved-filter changes before sprints or reports run against the wrong configuration.

Works with
Jira Cloud; board monitoring requires Jira Software
Status
Available on Atlassian Marketplace for Jira Cloud
Product page Docs Marketplace
Label Doctor screenshot from the Atlassian Marketplace listing showing Jira label cleanup and merge review workflows.

Jira label cleanup

Label Doctor

Find duplicate Jira labels, preview safe merges, and keep cleanup undoable.

Works with
Jira Cloud
Status
Available on Atlassian Marketplace for Jira Cloud
Product page Docs Marketplace

Solution

Jira Admin Cleanup and Governance

Jira admin work often fails in small places: over-shared filters, owner drift, label sprawl, and silent board changes. ArdSaor apps focus on these concrete cleanup and governance jobs with previews, audit records, and Forge-first architecture.

Filter Hygiene Label Doctor DriftGuard

Explore this solution