index.php (~lines 385-390), the ta subquery for the User Activity report: SELECT assigned_to, COUNT(*) ... FROM tickets WHERE DATE(created_at) BETWEEN ? AND ? GROUP BY assigned_to.
Impact: A ticket created outside the selected date range but assigned to a user within it won't count toward "Tickets Assigned"; conversely a ticket created inside the range but assigned/reassigned later still counts as if the assignment happened in-range. The column is filtered by the wrong date field for what it claims to measure, producing a misleading metric on /admin/user-activity.
Fix: If assignment date isn't tracked separately, either add an assigned_at timestamp column, derive it from audit_log assignment events, or relabel the column to clarify it's actually measuring tickets created-and-assigned-to in the range.
**Severity:** Medium
`index.php` (~lines 385-390), the `ta` subquery for the User Activity report: `SELECT assigned_to, COUNT(*) ... FROM tickets WHERE DATE(created_at) BETWEEN ? AND ? GROUP BY assigned_to`.
**Impact:** A ticket created outside the selected date range but assigned to a user within it won't count toward "Tickets Assigned"; conversely a ticket created inside the range but assigned/reassigned later still counts as if the assignment happened in-range. The column is filtered by the wrong date field for what it claims to measure, producing a misleading metric on `/admin/user-activity`.
**Fix:** If assignment date isn't tracked separately, either add an `assigned_at` timestamp column, derive it from `audit_log` assignment events, or relabel the column to clarify it's actually measuring tickets created-and-assigned-to in the range.
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: Medium
index.php(~lines 385-390), thetasubquery for the User Activity report:SELECT assigned_to, COUNT(*) ... FROM tickets WHERE DATE(created_at) BETWEEN ? AND ? GROUP BY assigned_to.Impact: A ticket created outside the selected date range but assigned to a user within it won't count toward "Tickets Assigned"; conversely a ticket created inside the range but assigned/reassigned later still counts as if the assignment happened in-range. The column is filtered by the wrong date field for what it claims to measure, producing a misleading metric on
/admin/user-activity.Fix: If assignment date isn't tracked separately, either add an
assigned_attimestamp column, derive it fromaudit_logassignment events, or relabel the column to clarify it's actually measuring tickets created-and-assigned-to in the range.