index.php (~lines 391-395): SELECT user_id, MAX(created_at) FROM audit_log GROUP BY user_id — this subquery has no WHERE clause on the selected date range at all, so it always shows true all-time last activity even when the page is filtered to e.g. "last 7 days," inconsistent with every other column on the same report.
Fix: Add the same date-range WHERE clause used by the report's other subqueries, or clearly label the column as "Last Activity (all-time)" if that's the intended behavior.
**Severity:** Low
`index.php` (~lines 391-395): `SELECT user_id, MAX(created_at) FROM audit_log GROUP BY user_id` — this subquery has no `WHERE` clause on the selected date range at all, so it always shows true all-time last activity even when the page is filtered to e.g. "last 7 days," inconsistent with every other column on the same report.
**Fix:** Add the same date-range `WHERE` clause used by the report's other subqueries, or clearly label the column as "Last Activity (all-time)" if that's the intended behavior.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: Low
index.php(~lines 391-395):SELECT user_id, MAX(created_at) FROM audit_log GROUP BY user_id— this subquery has noWHEREclause on the selected date range at all, so it always shows true all-time last activity even when the page is filtered to e.g. "last 7 days," inconsistent with every other column on the same report.Fix: Add the same date-range
WHEREclause used by the report's other subqueries, or clearly label the column as "Last Activity (all-time)" if that's the intended behavior.