Advanced Search priority range and date range have no min≤max validation #61

New Issue

2026-08-31T21:40:12-04:00

jared commented

2026-08-31 21:40:12 -04:00

Severity: Low

assets/js/advanced-search.js (~lines 90-99 date range, ~lines 108-112 priority range) — a user can set priority_min=5, priority_max=1, or an end-date before a start-date; nothing blocks it client- or server-side in this flow. It's just silently sent as an unsatisfiable range, returning zero results with no explanation to the user.

Fix: Add simple client-side validation (swap or clamp min/max, or disable submit with an inline message) before building the filter query string.

**Severity:** Low `assets/js/advanced-search.js` (~lines 90-99 date range, ~lines 108-112 priority range) — a user can set `priority_min=5, priority_max=1`, or an end-date before a start-date; nothing blocks it client- or server-side in this flow. It's just silently sent as an unsatisfiable range, returning zero results with no explanation to the user. **Fix:** Add simple client-side validation (swap or clamp min/max, or disable submit with an inline message) before building the filter query string.

jared added the priority/low ux labels 2026-09-08 10:15:46 -04:00

jared referenced this issue from a commit

2026-09-08 11:59:38 -04:00

Advanced Search: swap inverted date/priority ranges instead of submitting them (#61)

jared referenced this issue from a commit

2026-09-08 15:39:42 -04:00

Merge development into main: 15-issue triage + fix batch

Sign in to join this conversation.