The Issues tab

The Issues tab is where scan results land. On a project of any size the raw list is long, so most of this tab is about narrowing it to what matters right now.

Grouping

Group results three ways:

• Scene / Asset — everything wrong in one place. Best for “I’m working in this scene today.”
• Issue Type — every missing script together, every broken UnityEvent together. Best for batch fixing, since one fix strategy usually clears a whole group.
• Severity — Critical first. Best for triage.

Filtering

The filter panel narrows by severity, issue type, scene, component, and field. Filters combine, so “Critical missing references in the Gameplay scene” is one filter state.

Save any filter state as a preset and switch between them from the toolbar. Presets are per-user, stored in Library/RefSafePro/UserSettings.json.

Search

The search box matches across scene name, component name, field name, and issue type at once. Searching Rigidbody finds every issue on a Rigidbody component regardless of which scene it’s in.

Row actions

Right-click any row:

Action	What it does
Copy	Copies the issue description to the clipboard
Ignore	Hides the issue indefinitely
Snooze	Hides it for 1, 7, or 30 days
Edit Note	Attaches free-form text to the issue
Replace	Opens the smart-replacement dropdown (missing references)
Find References	Jumps to the References tab for the affected asset

Clicking a row selects and pings the object in the Hierarchy or Project window.

Inline help

Expand a row to see what the issue means, the Component.field it originated from, any note you’ve attached, and a snooze countdown if one is active. Where Unity documents the underlying concept, the expander links to the relevant manual page.

Pinning

Pin an issue and it floats to the top of its group and stays there across scans. Useful for the two or three things you’re actively working on inside a list of hundreds.

Pins are stored per-user by issue hash, so they survive re-scans as long as the issue itself is unchanged.

Snooze vs. ignore

Both hide an issue. The difference is whether it comes back.

Snooze sets an expiry — 1, 7, or 30 days. Use it for “not this sprint.” The issue returns automatically, which is the point.

Ignore has no expiry. Use it for accepted issues: an asset loaded through Resources.Load that the unused-asset detector can’t see, a duplicate component that’s genuinely intentional. Add a note explaining why, so the next person to read the list doesn’t undo your decision.

Both are per-user and stay out of version control. A teammate’s ignore list never hides an issue from you.

Density

Toggle between Comfortable and Compact row density from the toolbar. Compact fits substantially more rows on screen, which matters during a triage pass.

Diff indicators

After a scan, rows are marked as new, existing, or resolved relative to the previous scan. Sorting by “new” surfaces regressions introduced since you last looked — usually the most urgent thing in the list.