Skip to main content

How to read and export REQQA's metrics

When you'd do this: whenever you want a current picture of open-issue risk for an application, or to pull the underlying numbers into a spreadsheet or another tool.

REQQA stores build and quality metrics — issue counts, analysis throughput, and whatever else a producer posts — in one generic time-series table (FR-25.1). The Metrics page gives you a curated, organisation-scoped read over that store, plus a CSV export that matches whatever filter is on screen.

note

There is no menu link to this page yet — go to /metricsReport directly. The same is true of the codebook and declaration pages (see their own how-tos).

Step 1 — Open the Metrics page​

Go to /metricsReport. Everything on it is scoped to your organisation — you'll never see another organisation's data, and there is no way to ask for one via the URL.

Step 2 — Filter​

Use the filter bar at the top:

  • Application — narrow to one application, or leave on "All applications"
  • From / To — a date range, applied to the captured_at of each observation

Changing any filter reloads the page immediately (there's no separate "Apply" button). Click Clear Filters to go back to the unfiltered view.

Step 3 — Read the Open-Issue Risk Profile​

This is the flagship view: a live count of open analysis issues for the current filter, broken down by severity.

  • Open issues — everything currently Open. Superseded issues are shown separately and never counted here — re-running an analysis doesn't inflate this number.
  • HIGH / MEDIUM / LOW severity — the same open count, split by severity
  • No severity recorded (legacy) — only appears if some open issues predate severity capture; shown so an old, unclassified issue is never silently folded into a severity bucket it was never actually given

A one-line statement under the tiles spells out exactly what "Open" means for this count — read it if you're ever unsure whether a particular issue status is included.

Step 4 — Read Analysis Throughput​

Below the risk profile, a table of recent issues_per_requirement, severity_distribution, and deterministic_finding_share observations — posted automatically every time an analysis completes (FR-25.6). This is currently the only throughput-style series with a real producer behind it.

note

Issue burn-down, regression pass rate across releases, and requirements-vs-stories churn are named in the requirement but have no posting producer yet — the page says so explicitly ("Not Yet Available") rather than omitting them silently. If you're testing and these look empty, that's expected, not a bug.

Step 5 — Export to CSV​

Each section has its own Export CSV link, next to its heading:

  • Open-Issue Risk Profile exports as a one-row summary (open_issue_risk_profile.csv)
  • Analysis Throughput exports every matching row for the three posted series (<series>_export.csv), using the same filters as the page — not capped to the 100 rows shown on screen

You can also build your own export URL directly: /metricsExportCsv?series=<metric_name> plus any of appid=, scope_id=, start=, end=. An unknown series value returns a CSV with just a header row, not an error.

Result​

A filtered, exportable view of open-issue risk and analysis throughput for your organisation, with an honest statement of what isn't tracked yet rather than a silently empty chart.