fix: Suggestion - allow multiple statuses in the search for PO history #33

Merged

shad0w merged 2 commits from claude/issue-31 into master

2026-06-19 07:00:32 +00:00

shad0w commented

2026-06-19 06:23:54 +00:00

Owner

Automated fix by Claude Code for #31.

Closes #31

Review, merge, then create a release tag (vX.Y.Z) to deploy.

Automated fix by Claude Code for #31. Closes #31 Review, merge, then create a release tag (vX.Y.Z) to deploy.

shad0w added 1 commit 2026-06-19 06:23:55 +00:00

feat(history): allow filtering PO history by multiple statuses e94c7f99a3

The PO history page previously allowed only a single status filter. This
enhances it to accept multiple statuses that are OR-ed together (e.g.
Closed + Approved shows all POs in either state), as requested.

- Status filter is now a multi-select checkbox dropdown that serialises
  selections as repeated `status` query params.
- History page and the reports export endpoint read all `status` values
  and query with `status: { in: [...] }` (OR semantics).
- Single-status and no-status cases remain unchanged.

Verified OR-query semantics against the test DB and confirmed both routes
compile and respond. type-check passes for the changed files.

Fixes #31

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>