Skip to main content
The Issues view shows every open finding for the project’s tracked branch in a filterable, sortable table. It’s the primary place to triage, prioritise, and (where supported) resolve issues across all of Qlty’s static analysis, security, and maintainability checks. By default the table shows issues with status = open, sorted by priority descending.

​
Filters

The view supports faceted filtering. Each filter is a list of values — selecting any value within a facet ORs across that facet, while selecting values across different facets ANDs.
  • Status — open (default), ignored, or all. Ignored covers issues you’ve dismissed in the web app (with a reason such as false_positive or wont_fix) or silenced through qlty.toml.
  • Category — bug, vulnerability, structure, duplication, security_hotspot, performance, documentation, type_check, style, anti_pattern, accessibility, dead_code, lint, secret, dependency_alert.
  • Level — note, fmt, low, medium, high.
  • Tool — the plugin or analyzer that surfaced the issue (eslint, rubocop, semgrep, etc.).
  • Language — the file’s programming language.
There’s also a free-text search box for matching against issue messages and file paths. The URL captures the current filter and sort state, so any view is shareable as a link.

​
Acting on an issue

Click into any row to see the full issue page, which includes:
  • The issue message, rule, and tool that reported it.
  • A code snippet showing the affected lines.
  • The category, [level](/cloud/maintainability/metrics#issue-levels, and mode applied to this finding.
  • Available actions — open a GitHub Issue, mark as Ignored, or jump to the source file on GitHub.
If you’ve enabled AI Autofixes, you can request a fix suggestion directly from the issue page.

​
See Also